Efficient and reliable data transfer in 5g systems

ABSTRACT

Systems and methods provide solutions for reliable data transfer in a mobile communication network. A user equipment (UE) may indicate to the mobile communication network a capability of the UE to support a reliable data service protocol. The UE may process non-access stratum (NAS) messages, for both mobile originated (MO) data transfer and mobile terminated (MT) data transfer, using the reliable data service protocol to determine whether protocol data units (PDUs) of the NAS messages require no acknowledgement, require acknowledgment, or include an acknowledgement, and to detect and eliminate duplicate PDUs received at the UE in the NAS messages.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/406,973, filed May 8, 2019, which is a continuation of U.S. patentapplication Ser. No. 16/279,804, filed Feb. 19, 2019, which claims thebenefit of U.S. Provisional Patent Application No. 62/632,561, filedFeb. 20, 2018, which are hereby incorporated by reference herein intheir entirety.

TECHNICAL BACKGROUND

This application relates generally to wireless communication systems,and more specifically to reliable data service for unstructured data.

BACKGROUND

Wireless mobile communication technology uses various standards andprotocols to transmit data between a base station and a wireless mobiledevice. Wireless communication system standards and protocols caninclude the 3rd Generation Partnership Project (3GPP) long termevolution (LTE); the Institute of Electrical and Electronics Engineers(IEEE) 802.16 standard, which is commonly known to industry groups asworldwide interoperability for microwave access (WiMAX); and the IEEE802.11 standard for wireless local area networks (WLAN), which iscommonly known to industry groups as Wi-Fi. In 3GPP radio accessnetworks (RANs) in LTE systems, the base station can include a RAN Nodesuch as a Evolved Universal Terrestrial Radio Access Network (E-UTRAN)Node B (also commonly denoted as evolved Node B, enhanced Node B,eNodeB, or eNB) and/or Radio Network Controller (RNC) in an E-UTRAN,which communicate with a wireless communication device, known as userequipment (UE). In fifth generation (5G) wireless RANs, RAN Nodes caninclude a 5G Node, new radio (NR) node or g Node B (gNB).

RANs use a radio access technology (RAT) to communicate between the RANNode and UE. RANs can include global system for mobile communications(GSM), enhanced data rates for GSM evolution (EDGE) RAN (GERAN),Universal Terrestrial Radio Access Network (UTRAN), and/or E-UTRAN,which provide access to communication services through a core network.Each of the RANs operates according to a specific 3GPP RAT. For example,the GERAN implements GSM and/or EDGE RAT, the UTRAN implements universalmobile telecommunication system (UMTS) RAT or other 3GPP RAT, and theE-UTRAN implements LTE RAT.

A core network can be connected to the UE through the RAN Node. The corenetwork can include a serving gateway (SGW), a packet data network (PDN)gateway (PGW), an access network detection and selection function(ANDSF) server, an enhanced packet data gateway (ePDG) and/or a mobilitymanagement entity (MME).

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

To easily identify the discussion of any particular element or act, themost significant digit or digits in a reference number refer to thefigure number in which that element is first introduced.

FIG. 1 illustrates an example non-roaming architecture for reliable dataservice (RDS) using service-based interfaces within a control plane inaccordance with one embodiment.

FIG. 2 illustrates an example non-roaming architecture to support RDSusing reference point representation in accordance with one embodiment.

FIG. 3 illustrates a roaming architecture to support RDS usingservice-based interfaces within the control plane in accordance with oneembodiment.

FIG. 4 illustrates a roaming architecture to support RDS using thereference point representation in accordance with one embodiment.

FIG. 5 illustrates an RDS configuration procedure in accordance with oneembodiment.

FIG. 6 illustrates an MO data delivery procedure in accordance with oneembodiment.

FIG. 7 illustrates an MT data delivery procedure in accordance with oneembodiment.

FIG. 8 illustrates a registration procedure supporting RDS delivery overNAS in accordance with one embodiment.

FIG. 9 illustrates a system in accordance with one embodiment.

FIG. 10 illustrates a system in accordance with one embodiment.

FIG. 11 illustrates a device in accordance with one embodiment.

FIG. 12 illustrates an example interfaces in accordance with oneembodiment.

FIG. 13 illustrates a control plane in accordance with one embodiment.

FIG. 14 illustrates a user plane in accordance with one embodiment.

FIG. 15 illustrates components in accordance with one embodiment.

FIG. 16 illustrates a system in accordance with one embodiment.

FIG. 17 illustrates components in accordance with one embodiment.

DETAILED DESCRIPTION

A detailed description of systems and methods consistent withembodiments of the present disclosure is provided below. While severalembodiments are described, it should be understood that the disclosureis not limited to any one embodiment, but instead encompasses numerousalternatives, modifications, and equivalents. In addition, whilenumerous specific details are set forth in the following description inorder to provide a thorough understanding of the embodiments disclosedherein, some embodiments can be practiced without some or all of thesedetails. Moreover, for the purpose of clarity, certain technicalmaterial that is known in the related art has not been described indetail in order to avoid unnecessarily obscuring the disclosure.

3GPP technical reference (TR) 23.724 on cellular internet of things(CIoT) support and evolution for 5G systems lists several requirements,including solutions to support efficient infrequent small datatransmissions for low complexity, power constrained, low-mobility, andlow data-rate CIoT UEs. Further there is a need to enable Reliable DataService for unstructured data. As used herein, unstructured data mayalso be referred to as non-IP data.

Some of these requirements include a resource efficient system signalingload (especially over the Radio interface) with support forsingle/dual/multiple packet transmission (uplink (UL) or downlink (DL)).There is a need to support delivery of IP data and Unstructured (Non-IP)data. For non-IP data delivery (NIDD) of unstructured protocol dataunits (PDUs), there is a need to provide for reliability and thedetection and elimination of duplicate packets. The sender may need, forexample, to indicate whether or not the data is to be sent withreliability or not, and it may be possible to identify the sending andreceiving application and indicate support for reliable communication.

Embodiments herein provide mechanisms for reliable (infrequent) smalldata transfer in 5G systems. In some embodiments, the Reliable DataProtocol (as specified in 3GPP technical specification (TS) 24.250)between UE and network exposure function (NEF) or other network entitysuch as user plane function (UPF), and non-access stratum (NAS)transport may be reused between UE and access and Mobility Managementfunction (AMF).

Support for Reliable Data Service (RDS) involves the use of NAStransport between UE and AMF for small data delivery. This applies toboth 3GPP and non-3GPP accesses. The AMF determines the NEF that isresponsible for exposing this functionality for a given UE and the NEFprovides support for subscription checking and actual transmission ofMO/MT small data delivery to the AF/UE. The mobile originated(MO)/mobile terminated (MT) small data can be delivered for both roamingand non-roaming scenarios.

In certain embodiments, during registration procedure, a UE that wantsto use RDS provides “RDS supported” indication over NAS signalingindicating the UE's capability for support of RDS. “RDS supported”indication indicates whether UE can support reliable small data deliveryover NAS via 3GPP access or via both 3GPP and non-3GPP access. If thecore network supports RDS functionality, the AMF includes “RDSsupported” indication to the UE, and whether RDS delivery over NAS via3GPP access or via both the 3GPP and non-3GPP access is accepted by thenetwork. In other embodiments, the UE indicates its support for RDS inother ways. For example, in one embodiment, the UE indicates itscapability of supporting RDS in protocol configuration options (PCO) andthe SMF negotiates RDS support with the NEF or UPF. If the NEF or UPFsupports and accepts RES, then the network indicates to the UE in thePCO that RDS will be used if enabled in the data network name (DNN) andnetwork slice selection assistance information (NSSAI) configuration.

In certain embodiments, RDS packets are transmitted over NAS without theneed to establish data radio bearers, via NAS transport message, whichcan carry RDS payload. UE and Network supports RDS protocol as specifiedin 3GPP TS 24.250.

In certain embodiments, “RDS Supported” (or similar indication e.g.“Small Data over NAS supported”) is provided by UE to the (R)AN node(e.g. gNB) during RRC connection establishment (e.g., in an RRCmessage), which is used by gNB for appropriate AMF selection.

In certain embodiments, when reliability is not needed or provided at anapplication layer, small data may be transferred using the samemechanism. In this case Reliable Data Protocol (as specified in TS24.250) between UE and AMF is not needed. In this case instead of “RDSsupported,” other indication for “Small Data over NAS supported”indication may be provided. In certain embodiments such NAS indicationmay be referred by other names.

Certain embodiments herein do not require establishment of a PDU sessionand can transfer data over control plane connection. This savessignaling for PDU session establishment. However in certain embodiments,the solution may rely on PDU session establishment of type “unstructureddata” for reliable small data transfer. In such embodiments, AMFinteracts with SMF for PDU session establishment prior to sending andreceiving data. Such interactions are not shown in the architecturaldiagram and procedures for the sake of simplicity, but are furtherexplained where needed. RDS between the UE and NEF or UPF when using aPDU session of PDU Type “unstructured” provides a mechanism for the NEFor UPF to determine if the data was successfully delivered to the UE andfor UE to determine if the data was successfully delivered to the NEF orUPF. When a requested acknowledgement is not received, the RDSretransmits the packet. The service is enabled or disabled based on DNNand NSSAI configuration per service level agreement (SLA). When theservice is enabled, a protocol is used between the end-points of theunstructured PDU Session. The protocol uses a packet header to identifyif the packet requires no acknowledgement, requires an acknowledgement,or is an acknowledgment and to allow detection and elimination ofduplicate PDUs at the receiving endpoint. Port Numbers in the header areused to identify the application on the originator and to identify theapplication on the receiver. The header is configured based on ReliableData Service configuration information which is obtained in the NIDDconfiguration, MT NIDD, and MO NIDD procedures with the AF as specifiedin TS 23.502.

In certain embodiments AMF (and/or NEF) may interact with policy controlfunction (PCF) instead of UDM/UDR for subscription information andpolicy related information. In certain embodiments for reliable smalldata delivery actions performed by NEF in this disclosure may bereplaced by other functional entity (e.g., PCF).

FIG. 1 illustrates an example non-roaming architecture 100 for RDS usingservice-based interfaces within a control plane according to oneembodiment. The example non-roaming architecture 100 comprises an AF102, an AMF 104, a NEF 106, a UDR/UDM 108, and a UE 110 andcorresponding interfaces Naf, Nnef, Nudm, Namf, and N1. Additionaldescription of architectures with service-based interfaces is providedherein below.

FIG. 2 illustrates an example non-roaming architecture 200 to supportRDS using reference point representation in accordance with oneembodiment. The example non-roaming architecture 200 comprises a UE 110,an AMF 104, a UDR/UDM 108, a NEF 106, and an AF/AS 202 and correspondingreference points N1, N8, Nxx, Nyy, and N33. Additional architecturedetails are provided below.

FIG. 3 illustrates a roaming architecture 300 to support RDS usingservice-based interfaces within the control plane in accordance with oneembodiment. The roaming architecture 300 comprises an AF 102, a NEF 106,a UDR/UDM 108, an AMF 104, and a UE 110 and corresponding interfacesNaf, Nnef, Nudm, N1, and Namf. The UDR/UDM 108 is shown within a homepublic land mobile network (HPLMN) and the AF 102, NEF 106, AMF 104, andUE 110 are shown within a visited public land mobile network (VPLMN).

FIG. 4 illustrates a roaming architecture 400 to support RDS using thereference point representation in accordance with one embodiment. Theroaming architecture 400 comprises a UE 110, an AMF 104, a NEF 106, anAF/AS 202, and a UDR/UDM 108 and corresponding reference points N1, Nxx,N33, N8, and Nyy. The UDR/UDM 108 is shown within an HPLMN and the UE110, AMF 104, NEF 106, and AF/AS 202 are shown within a VPLMN. In thisdisclosure, Nxx is new reference point between the AMF 104 and the NEF106, and Nyy is a new reference point between the NEF 106 and theUDR/UDM 108. In various embodiments, the NEF 106 may also use directlyservices from a UDR (without involving the UDR/UDM 108) via the Nyyreference point.

In certain embodiments that provide PDU session establishment prior tosmall data transfer, the AMF 104 interacts with an SMF (not shown inFIG. 4) via N11 reference point (for non-roaming) and via N11/N16reference point (for roaming). In service based architecture, the SMF isconnected via Nsmf reference point to the message bus.

When the RDS is enabled, a protocol is used between the end-points,i.e., between the UE 110 and the NEF 106. In certain embodiments, theprotocol uses an RDS header to identify if the packet requires noacknowledgement, requires an acknowledgement, or is an acknowledgmentand to allow detection and elimination of duplicate PDUs at thereceiving endpoint. Also port numbers in the header are used to identifythe application on the originator and to identify the application on thereceiver.

FIG. 5 illustrates an RDS configuration procedure 500 between a NEF 106and an AF/AS 202 in accordance with one embodiment. The RDSconfiguration procedure 500 is used to configure information used forRDS at the NEF 106 and the UDR/UDM 108. In order to avoid MO reliablesmall data delivery failure, the RDS configuration procedure may beperformed, according to certain embodiments, by the AF/AS 202 prior tothe UE 110 requesting to send MO reliable small data delivery.

The AF/AS 202 uses a Nnef_RDSConfig Request 502 service operation toestablish routing information in UE context at the NEF 106. TheNnef_RDSConfig Request 502 may be referred to by other names, such as anNnef_NIDDConfiguration_Create Request. The AF/AS 202 provides anexternal identifier for UE message and reliable data serviceconfiguration information (e.g., application port number) to the NEF106. In certain embodiments, the request may include a general publicsubscription identifier (GPSI), an AF ID, a non-IP data delivery (NIDD)duration, and/or a T8 destination address. The NEF 106 may store theinformation provided in the request and may respond to the 202 with anindication that the AF/AS 202 is not authorized or the request ismalformed.

The NEF 106 uses a Nudr_UDM-Query Request 504 service operation to checkif RDS configuration request for the received external identifier isauthorized, and to receive necessary information for RDS, if required.The Nudr_UDM-Query Request 504 may be referred to by other names, suchas a Nudm_NIDDAuthorization_Get Request (e.g., to get authorization forUEs that belong to a GPSI, received external identifier, or mobilestationary international subscriber directory number (MSISDN), and toreceive information for NIDD). The UDR/UDM 108 examines theNudr_UDM-Query Request 504, e.g. with regard to the existence of theexternal identifier (or GPSI), and maps the external identifier (orGPSI) to a subscription permanent identifier (SUPI). The UDR/UDM 108 mayalso update a NEF ID filed of subscription data for a provided DNN andS-NSSAI with the requesting NEF's ID.

The UDR/UDM 108 sends a Nudr_UDM_Query Response 506 (including the SUPIand a Result) to the NEF 106 to acknowledge acceptance of the RDSauthorization. The Nudr_UDM_Query Response 506 may be referred to byother names, such as Nudm_NIDDAuthorization_Get Response (e.g.,including the SUPI, GPSI, and Result) to allow the NEF 106 to correlatethe AF request to an SMF-NEF connection establishment for each UE oreach group member UE.

The NEF 106 uses a Nnef_RDSConfig Response 508 service operation toacknowledge acceptance of the RDS configuration request to the AF/AS202. If the RDS configuration was accepted, the NEF 106 will create anassociation between the External Identifier and SUPI in UE context. Inthe MT reliable small data delivery procedure, the NEF 106 will useExternal Identifier to determine the SUPI and receiver port number. Inthe MO reliable small data delivery procedure, the NEF 106 will use theSUPI, to determine AS/AF address and application port number from the UEcontext. The Nnef_RDSConfig Response 508 may be referred to by othernames, such as an Nnef_NIDDConfiguration_Create Response, wherein in MTthe NEF 106 uses TLTRI and GPSI to determine the SUPI and PDU session IDof the PDU session for delivering non-IP data, and in MO the NEF 106uses the SUPI and PDU session ID to obtain the TLTRI and GPSI.

If PDU session establishment is needed prior to small data transfer, theAMF interacts with the SMF (not shown in FIG. 5) via N11 reference point(for non-roaming) and via N11/N16 reference point (for roaming). InService based architecture, the SMF may be connected via the Nsmfreference point to the message bus. If PDU session is establishedbetween UE and NEF, the NEF maintains the association of PDU session ID,UE External Identifier, UE Identity (e.g., SUPI), port number, and DNNfor routing UL/DL PDUs.

FIG. 6 illustrates an MO data delivery procedure 600 in accordance withone embodiment. The MO data delivery procedure 600 may be used, forexample, for MO reliable small data delivery. In certain embodiments,the MO data delivery procedure 600 shown in FIG. 6 assumes that the UE110 is registered with the network.

In certain embodiments, the UE 110 sends an integrity protected NAS PDUto the AMF 104 via an access node (AN) (shown as AN 602. The AN 602 maybe a 3GPP or non-3GPP access node. For example, in certain embodiments,the AN 602 is a NG-RAN (also referred to as a gNB, NR-RAN, etc.). TheNAS PDU carries the UL RDS PDU data and indication for reliable smalldata delivery. The UE 110 may also provide release assistanceinformation to the AMF 104 indicating if this is the last PDU. The AMF104 may use this information to release the connection with AN 602.

The AMF 104 performs check integrity and decrypts data process 608 tocheck the integrity of the incoming NAS PDU and decrypts the PDU data.

The AMF 104 determines the NEF 106 based on the UE context and performsa Namf_RDSTransfer service operation 610 to send the RDS PDU to the NEF106 along with UE identity (e.g., SUPI).

The NEF 106 sends the data PDU to the AF/AS 202 according to UE contextusing a Nnef_DataTransfer service operation 612.

The NEF 106 sends RDS acknowledgement to AMF usingNamf_Communication_Message_Transfer service operation 614.

The AMF 104 encrypts the RDS acknowledgement PDU and sends it to the UE110 in a DL NAS message 616.

NAS messages shown in FIG. 6 are used as examples only. Actual names forNAS messages may differ or different NAS messages may be used forsending and receiving RDS PDU/ACK.

In certain embodiments, PDU session is established between the UE 110and the NEF 106. In such embodiments, the following additionaloperations may be performed. The UE 110 may send a PDU session ID aspart of the initial NAS message 606, wherein the PDU session ID and/orthe uplink data may be ciphered. The AMF 104 determines an SMF 604(either home or visited) based on the PDU session ID and routes UL RDSPDU to the SMF 604 for the PDU session ID indicated by the UE 110 afterthe check integrity and decrypt data process 608. The SMF 604 sends RDSPDU to the NEF 106 or to a UPF.

FIG. 7 illustrates an MT data delivery procedure 700 in accordance withone embodiment. The MT data delivery procedure 700 may be used, forexample, for MT reliable data delivery. In certain embodiments, the MTdata delivery procedure 700 shown in FIG. 7 assumes that the AF/AS 202has performed an RDS configuration procedure.

In certain embodiments, the AF/AS 202 requests reliable small datadelivery using a Nnef DataTransfer service operation 702. The AF/AS 202provides an External Identifier, DL data PDU, and Reliable Dataconfiguration.

The NEF 106, based on UE context, determines UE identity from the UE'sExternal identifier. The NEF 106 determines if the AF/AS 202 requestedreliable small data delivery and adds RDS header to data PDU. The NEF106 sends the RDS PDU to the AMF 104 using aNamf_Communication_MessageTransfer service operation 704.

If the UE 110 is in connection management (CM)-IDLE state, the AMF 104buffers the RDS PDU and sends a paging message 706 to AN nodes. Then theUE 110 is paged by the AN nodes. The UE 110 responds to paging with aninitial NAS message 708. If, on the other hand, the UE 110 is not inCM-IDLE state, the paging message 706 and initial NAS message 708 areskipped.

The AMF 104 performs an encryption and integrity protection process 710to the RDS PDU.

The AMF 104 sends encrypted NAS PDU with RDS PDU to the AN 602 in a DLNAS message 712.

If RDS acknowledgment is requested (as indicated by RDS PDU headerreceived in the DL NAS message 712), the UE 110 sends RDS ACK to the AMF104. Then, the AMF 104 sends the RDS ACK to the NEF 106 and the NEF 106sends it to the AF/AS 202 (as shown in FIG. 6 of the MO reliable smalldata delivery procedure).

The NAS messages shown in FIG. 7 are used as examples only. Actual namesfor NAS messages may differ or different NAS messages may be used forsending and receiving RDS PDU/ACK.

In certain embodiments, PDU session is established between the UE 110and the NEF 106. In such embodiments, the following additionaloperations may be performed. The NEF 106 determines the PDU session IDcorresponding to the UE identity from the UE context in the NEF 106. TheNEF 106 routes DL RDS PDU to the SMF 604 for the PDU session ID. The SMF604 sends RDS PDU to the AMF 104 as shown in theNamf_Communication_MessageTransfer service operation 704.

FIG. 8 illustrates a registration procedure 800 supporting RDS deliveryover NAS in accordance with one embodiment. The illustrated registrationprocedure 800 is provided by way of example only. As discussed above, inother embodiments a UE may indicate its capability of supporting RDS inother ways, e.g., in the PCO. In the example shown in FIG. 8, theregistration procedure 800 includes interactions and communicationsbetween a UE 110, an AMF 104, a NEF 106, and a UDR/UDM 108. During aregistration procedure, such as the 5GS registration procedure definedin FIG. 4.2.2.2.2-1 of TS 23.502, to enable reliable small datadelivery, the UE 110 includes an “RDS supported” indication in aRegistration Request 802 in steps 1-3 of FIG. 4.2.2.2.2-1 of TS 23.502indicating the UE's capability for RDS. The “RDS supported” indicationindicates whether the UE 110 supports reliable small data delivery overNAS via current access.

Step 4 to step 14 of Registration Procedure 804 of FIG. 4.2.2.2.2-1 ofTS 23.502 are performed. When the AMF 104 relocation happens during theregistration procedure, the old AMF transfers NEF address to the new AMF104 as part of UE context in step 5 of FIG. 4.2.2.2.2-1.

In a NEF Selection 806, if the “RDS supported” indication is included inthe registration request, the AMF 104 checks subscription from theUDR/UDM 108 for the UE 110 on whether the RDS service is allowed to theUE 110. If yes and the UE context doesn't include an available NEF ofthe serving PLMN, the AMF 104 discovers and selects a NEF 106 to servethe UE 110. The NEF discovery is based on the following methods: NEFaddress preconfigured in the AMF 104 (i.e., NEF FQDN); or NEF addressreceived from the UDR/UDM 108; or the AMF 104 invokes Nnrf_NFDiscoveryservice operation from NRF to discover the NEF address as described inclause 5.2.7.3.2 of TS 23.502. For roaming scenario, the AMF 104discovers and selects a NEF in VPLMN.

Step 15 to step 20 of Registration Procedure 808 of FIG. 4.2.2.2.2-1 ofTS 23.502 are performed.

The AMF 104 invokes a Nnef_RDS_Activate_Request 810 operation from theNEF 106. The invocation includes AMF address, access Type, GPSI (ifavailable) and SUPI. The AMF 104 uses the NEF address derived from theNEF Selection 806.

The NEF 106 performs UDR discovery 812, as described in TS 23.501,clause 6.3.9.

If the UE context already exists in the NEF 106, the NEF 106 replacesthe old AMF address with the new AMF address. Otherwise, the NEF 106retrieves RDS related subscription data using Nudr_UDM_Query 816 andsubscribes to be notified using Nudr_UDM_notify 814 when the RDS relatedsubscription data is modified. The NEF 106 also creates a UE context tostore the RDS subscription information and the AMF address that isserving this UE 110.

The NEF 106 responds back to the AMF 104 with Nsmsf_SMService_Activateservice operation response message or Nnef_RDS_Activate Response 818.The AMF 104 stores the NEF address received as part of the UE context.

In certain embodiments, the AMF 104 includes the “RDS supported”indication to the UE 110 in the Registration Accept message of step 21of FIG. 4.2.2.2.2-1 of TS 23.502 only after the Nnef_RDS_ActivateResponse 818 in which the AMF 104 has received a positive indicationfrom the selected NEF 106. The “RDS supported” indication in theRegistration Accept 820 message indicates to the UE 110 whether thenetwork allows the reliable small message delivery over NAS via 3GPPaccess or via both the 3GPP and non-3GPP access.

FIG. 9 illustrates an architecture of a system 900 of a network inaccordance with some embodiments. The system 900 includes one or moreuser equipment (UE), shown in this example as a UE 902 and a UE 904. TheUE 902 and the UE 904 are illustrated as smartphones (e.g., handheldtouchscreen mobile computing devices connectable to one or more cellularnetworks), but may also comprise any mobile or non-mobile computingdevice, such as Personal Data Assistants (PDAs), pagers, laptopcomputers, desktop computers, wireless handsets, or any computing deviceincluding a wireless communications interface.

In some embodiments, any of the UE 902 and the UE 904 can comprise anInternet of Things (IoT) UE, which can comprise a network access layerdesigned for low-power IoT applications utilizing short-lived UEconnections. An IoT UE can utilize technologies such asmachine-to-machine (M2M) or machine-type communications (MTC) forexchanging data with an MTC server or device via a public land mobilenetwork (PLMN), Proximity-Based Service (ProSe) or device-to-device(D2D) communication, sensor networks, or IoT networks. The M2M or MTCexchange of data may be a machine-initiated exchange of data. An IoTnetwork describes interconnecting IoT UEs, which may include uniquelyidentifiable embedded computing devices (within the Internetinfrastructure), with short-lived connections. The IoT UEs may executebackground applications (e.g., keep-alive messages, status updates,etc.) to facilitate the connections of the IoT network.

The UE 902 and the UE 904 may be configured to connect, e.g.,communicatively couple, with a radio access network (RAN), shown as RAN906. The RAN 906 may be, for example, an Evolved Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access Network(E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. The UE 902and the UE 904 utilize connection 908 and connection 910, respectively,each of which comprises a physical communications interface or layer(discussed in further detail below); in this example, the connection 908and the connection 910 are illustrated as an air interface to enablecommunicative coupling, and can be consistent with cellularcommunications protocols, such as a Global System for MobileCommunications (GSM) protocol, a code-division multiple access (CDMA)network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular(POC) protocol, a Universal Mobile Telecommunications System (UMTS)protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation(5G) protocol, a New Radio (NR) protocol, and the like.

In this embodiment, the UE 902 and the UE 904 may further directlyexchange communication data via a ProSe interface 912. The ProSeinterface 912 may alternatively be referred to as a sidelink interfacecomprising one or more logical channels, including but not limited to aPhysical Sidelink Control Channel (PSCCH), a Physical Sidelink SharedChannel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and aPhysical Sidelink Broadcast Channel (PSBCH).

The UE 904 is shown to be configured to access an access point (AP),shown as AP 914, via connection 916. The connection 916 can comprise alocal wireless connection, such as a connection consistent with any IEEE802.11 protocol, wherein the AP 914 would comprise a wireless fidelity(WiFi®) router. In this example, the AP 914 may be connected to theInternet without connecting to the core network of the wireless system(described in further detail below).

The RAN 906 can include one or more access nodes that enable theconnection 908 and the connection 910. These access nodes (ANs) can bereferred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), nextGeneration NodeBs (gNB), RAN nodes, and so forth, and can compriseground stations (e.g., terrestrial access points) or satellite stationsproviding coverage within a geographic area (e.g., a cell). The RAN 906may include one or more RAN nodes for providing macrocells, e.g., macroRAN node 918, and one or more RAN nodes for providing femtocells orpicocells (e.g., cells having smaller coverage areas, smaller usercapacity, or higher bandwidth compared to macrocells), e.g., a low power(LP) RAN node such as LP RAN node 920.

Any of the macro RAN node 918 and the LP RAN node 920 can terminate theair interface protocol and can be the first point of contact for the UE902 and the UE 904. In some embodiments, any of the macro RAN node 918and the LP RAN node 920 can fulfill various logical functions for theRAN 906 including, but not limited to, radio network controller (RNC)functions such as radio bearer management, uplink and downlink dynamicradio resource management and data packet scheduling, and mobilitymanagement.

In accordance with some embodiments, the UE 902 and the UE 904 can beconfigured to communicate using Orthogonal Frequency-DivisionMultiplexing (OFDM) communication signals with each other or with any ofthe macro RAN node 918 and the LP RAN node 920 over a multicarriercommunication channel in accordance various communication techniques,such as, but not limited to, an Orthogonal Frequency-Division MultipleAccess (OFDMA) communication technique (e.g., for downlinkcommunications) or a Single Carrier Frequency Division Multiple Access(SC-FDMA) communication technique (e.g., for uplink and ProSe orsidelink communications), although the scope of the embodiments is notlimited in this respect. The OFDM signals can comprise a plurality oforthogonal subcarriers.

In some embodiments, a downlink resource grid can be used for downlinktransmissions from any of the macro RAN node 918 and the LP RAN node 920to the UE 902 and the UE 904, while uplink transmissions can utilizesimilar techniques. The grid can be a time-frequency grid, called aresource grid or time-frequency resource grid, which is the physicalresource in the downlink in each slot. Such a time-frequency planerepresentation is a common practice for OFDM systems, which makes itintuitive for radio resource allocation. Each column and each row of theresource grid corresponds to one OFDM symbol and one OFDM subcarrier,respectively. The duration of the resource grid in the time domaincorresponds to one slot in a radio frame. The smallest time-frequencyunit in a resource grid is denoted as a resource element. Each resourcegrid comprises a number of resource blocks, which describe the mappingof certain physical channels to resource elements. Each resource blockcomprises a collection of resource elements; in the frequency domain,this may represent the smallest quantity of resources that currently canbe allocated. There are several different physical downlink channelsthat are conveyed using such resource blocks.

The physical downlink shared channel (PDSCH) may carry user data andhigher-layer signaling to the UE 902 and the UE 904. The physicaldownlink control channel (PDCCH) may carry information about thetransport format and resource allocations related to the PDSCH channel,among other things. It may also inform the UE 902 and the UE 904 aboutthe transport format, resource allocation, and H-ARQ (Hybrid AutomaticRepeat Request) information related to the uplink shared channel.Typically, downlink scheduling (assigning control and shared channelresource blocks to the UE 904 within a cell) may be performed at any ofthe macro RAN node 918 and the LP RAN node 920 based on channel qualityinformation fed back from any of the UE 902 and UE 904. The downlinkresource assignment information may be sent on the PDCCH used for (e.g.,assigned to) each of the UE 902 and the UE 904.

The PDCCH may use control channel elements (CCEs) to convey the controlinformation. Before being mapped to resource elements, the PDCCHcomplex-valued symbols may first be organized into quadruplets, whichmay then be permuted using a sub-block interleaver for rate matching.Each PDCCH may be transmitted using one or more of these CCEs, whereeach CCE may correspond to nine sets of four physical resource elementsknown as resource element groups (REGs). Four Quadrature Phase ShiftKeying (QPSK) symbols may be mapped to each REG. The PDCCH can betransmitted using one or more CCEs, depending on the size of thedownlink control information (DCI) and the channel condition. There canbe four or more different PDCCH formats defined in LTE with differentnumbers of CCEs (e.g., aggregation level, L=1, 2, 4, or 8).

Some embodiments may use concepts for resource allocation for controlchannel information that are an extension of the above-describedconcepts. For example, some embodiments may utilize an enhanced physicaldownlink control channel (EPDCCH) that uses PDSCH resources for controlinformation transmission. The EPDCCH may be transmitted using one ormore enhanced the control channel elements (ECCEs). Similar to above,each ECCE may correspond to nine sets of four physical resource elementsknown as enhanced resource element groups (EREGs). An ECCE may haveother numbers of EREGs in some situations.

The RAN 906 is communicatively coupled to a core network (CN), shown asCN 928, via an S1 interface 922. In embodiments, the CN 928 may be anevolved packet core (EPC) network, a NextGen Packet Core (NPC) network,or some other type of CN. In this embodiment the S1 interface 922 issplit into two parts: the S1-U interface 924, which carries traffic databetween the macro RAN node 918 and the LP RAN node 920 and a servinggateway (S-GW), shown as S-GW 932, and an S1-mobility management entity(MME) interface, shown as S1-MME interface 926, which is a signalinginterface between the macro RAN node 918 and LP RAN node 920 and theMME(s) 930.

In this embodiment, the CN 928 comprises the MME(s) 930, the S-GW 932, aPacket Data Network (PDN) Gateway (P-GW) (shown as P-GW 934), and a homesubscriber server (HSS) (shown as HSS 936). The MME(s) 930 may besimilar in function to the control plane of legacy Serving GeneralPacket Radio Service (GPRS) Support Nodes (SGSN). The MME(s) 930 maymanage mobility aspects in access such as gateway selection and trackingarea list management. The HSS 936 may comprise a database for networkusers, including subscription-related information to support the networkentities' handling of communication sessions. The CN 928 may compriseone or several HSS 936, depending on the number of mobile subscribers,on the capacity of the equipment, on the organization of the network,etc. For example, the HSS 936 can provide support for routing/roaming,authentication, authorization, naming/addressing resolution, locationdependencies, etc.

The S-GW 932 may terminate the S1 interface 322 towards the RAN 906, androutes data packets between the RAN 906 and the CN 928. In addition, theS-GW 932 may be a local mobility anchor point for inter-RAN nodehandovers and also may provide an anchor for inter-3GPP mobility. Otherresponsibilities may include lawful intercept, charging, and some policyenforcement.

The P-GW 934 may terminate an SGi interface toward a PDN. The P-GW 934may route data packets between the CN 928 (e.g., an EPC network) andexternal networks such as a network including the application server 942(alternatively referred to as application function (AF)) via an InternetProtocol (IP) interface (shown as IP communications interface 938).Generally, an application server 942 may be an element offeringapplications that use IP bearer resources with the core network (e.g.,UMTS Packet Services (PS) domain, LTE PS data services, etc.). In thisembodiment, the P-GW 934 is shown to be communicatively coupled to anapplication server 942 via an IP communications interface 938. Theapplication server 942 can also be configured to support one or morecommunication services (e.g., Voice-over-Internet Protocol (VoIP)sessions, PTT sessions, group communication sessions, social networkingservices, etc.) for the UE 902 and the UE 904 via the CN 928.

The P-GW 934 may further be a node for policy enforcement and chargingdata collection. A Policy and Charging Enforcement Function (PCRF)(shown as PCRF 940) is the policy and charging control element of the CN928. In a non-roaming scenario, there may be a single PCRF in the HomePublic Land Mobile Network (HPLMN) associated with a UE's InternetProtocol Connectivity Access Network (IP-CAN) session. In a roamingscenario with local breakout of traffic, there may be two PCRFsassociated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within aHPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land MobileNetwork (VPLMN). The PCRF 940 may be communicatively coupled to theapplication server 942 via the P-GW 934. The application server 942 maysignal the PCRF 940 to indicate a new service flow and select theappropriate Quality of Service (QoS) and charging parameters. The PCRF940 may provision this rule into a Policy and Charging EnforcementFunction (PCEF) (not shown) with the appropriate traffic flow template(TFT) and QoS class of identifier (QCI), which commences the QoS andcharging as specified by the application server 942.

FIG. 10 illustrates an architecture of a system 1000 of a network inaccordance with some embodiments. The system 1000 is shown to include aUE 1002, which may be the same or similar to the UE 902 and the UE 904discussed previously; a 5G access node or RAN node (shown as (R)AN node1008), which may be the same or similar to the macro RAN node 918 and/orthe LP RAN node 920 discussed previously; a User Plane Function (shownas UPF 1004); a Data Network (DN 1006), which may be, for example,operator services, Internet access or 3rd party services; and a 5G CoreNetwork (5GC) (shown as CN 1010).

The CN 1010 may include an Authentication Server Function (AUSF 1014); aCore Access and Mobility Management Function (AMF 1012); a SessionManagement Function (SMF 1018); a Network Exposure Function (NEF 1016);a Policy Control Function (PCF 1022); a Network Function (NF) RepositoryFunction (NRF 1020); a Unified Data Management (UDM 1024); and anApplication Function (AF 1026). The CN 1010 may also include otherelements that are not shown, such as a Structured Data Storage networkfunction (SDSF), an Unstructured Data Storage network function (UDSF),and the like.

The UPF 1004 may act as an anchor point for intra-RAT and inter-RATmobility, an external PDU session point of interconnect to DN 1006, anda branching point to support multi-homed PDU session. The UPF 1004 mayalso perform packet routing and forwarding, packet inspection, enforceuser plane part of policy rules, lawfully intercept packets (UPcollection); traffic usage reporting, perform QoS handling for userplane (e.g. packet filtering, gating, UL/DL rate enforcement), performUplink Traffic verification (e.g., SDF to QoS flow mapping), transportlevel packet marking in the uplink and downlink, and downlink packetbuffering and downlink data notification triggering. UPF 1004 mayinclude an uplink classifier to support routing traffic flows to a datanetwork. The DN 1006 may represent various network operator services,Internet access, or third party services. DN 1006 may include, or besimilar to the application server 942 discussed previously.

The AUSF 1014 may store data for authentication of UE 1002 and handleauthentication related functionality. The AUSF 1014 may facilitate acommon authentication framework for various access types.

The AMF 1012 may be responsible for registration management (e.g., forregistering UE 1002, etc.), connection management, reachabilitymanagement, mobility management, and lawful interception of AMF-relatedevents, and access authentication and authorization. AMF 1012 mayprovide transport for SM messages for the SMF 1018, and act as atransparent proxy for routing SM messages. AMF 1012 may also providetransport for short message service (SMS) messages between UE 1002 andan SMS function (SMSF) (not shown by FIG. 10). AMF 1012 may act asSecurity Anchor Function (SEA), which may include interaction with theAUSF 1014 and the UE 1002, receipt of an intermediate key that wasestablished as a result of the UE 1002 authentication process. WhereUSIM based authentication is used, the AMF 1012 may retrieve thesecurity material from the AUSF 1014. AMF 1012 may also include aSecurity Context Management (SCM) function, which receives a key fromthe SEA that it uses to derive access-network specific keys.Furthermore, AMF 1012 may be a termination point of RAN CP interface (N2reference point), a termination point of NAS (NI) signaling, and performNAS ciphering and integrity protection.

AMF 1012 may also support NAS signaling with a UE 1002 over an N3interworking-function (IWF) interface. The N3IWF may be used to provideaccess to untrusted entities. N3IWF may be a termination point for theN2 and N3 interfaces for control plane and user plane, respectively, andas such, may handle N2 signaling from SMF and AMF for PDU sessions andQoS, encapsulate/de-encapsulate packets for IPSec and N3 tunneling, markN3 user-plane packets in the uplink, and enforce QoS corresponding to N3packet marking taking into account QoS requirements associated to suchmarking received over N2. N3IWF may also relay uplink and downlinkcontrol-plane NAS (NI) signaling between the UE 1002 and AMF 1012, andrelay uplink and downlink user-plane packets between the UE 1002 and UPF1004. The N3IWF also provides mechanisms for IPsec tunnel establishmentwith the UE 1002.

The SMF 1018 may be responsible for session management (e.g., sessionestablishment, modify and release, including tunnel maintain between UPFand AN node); UE IP address allocation & management (including optionalAuthorization); Selection and control of UP function; Configures trafficsteering at UPF to route traffic to proper destination; termination ofinterfaces towards Policy control functions; control part of policyenforcement and QoS; lawful intercept (for SM events and interface to LISystem); termination of SM parts of NAS messages; downlink DataNotification; initiator of AN specific SM information, sent via AMF overN2 to AN; determine SSC mode of a session. The SMF 1018 may include thefollowing roaming functionality: handle local enforcement to apply QoSSLAB (VPLMN); charging data collection and charging interface (VPLMN);lawful intercept (in VPLMN for SM events and interface to LI System);support for interaction with external DN for transport of signaling forPDU session authorization/authentication by external DN.

The NEF 1016 may provide means for securely exposing the services andcapabilities provided by 3GPP network functions for third party,internal exposure/re-exposure, Application Functions (e.g., AF 1026),edge computing or fog computing systems, etc. In such embodiments, theNEF 1016 may authenticate, authorize, and/or throttle the AFs. NEF 1016may also translate information exchanged with the AF 1026 andinformation exchanged with internal network functions. For example, theNEF 1016 may translate between an AF-Service-Identifier and an internal5GC information. NEF 1016 may also receive information from othernetwork functions (NFs) based on exposed capabilities of other networkfunctions. This information may be stored at the NEF 1016 as structureddata, or at a data storage NF using a standardized interfaces. Thestored information can then be re-exposed by the NEF 1016 to other NFsand AFs, and/or used for other purposes such as analytics.

The NRF 1020 may support service discovery functions, receive NFDiscovery Requests from NF instances, and provide the information of thediscovered NF instances to the NF instances. NRF 1020 also maintainsinformation of available NF instances and their supported services.

The PCF 1022 may provide policy rules to control plane function(s) toenforce them, and may also support unified policy framework to governnetwork behavior. The PCF 1022 may also implement a front end (FE) toaccess subscription information relevant for policy decisions in a UDRof UDM 1024.

The UDM 1024 may handle subscription-related information to support thenetwork entities' handling of communication sessions, and may storesubscription data of UE 1002. The UDM 1024 may include two parts, anapplication FE and a User Data Repository (UDR). The UDM may include aUDM FE, which is in charge of processing of credentials, locationmanagement, subscription management and so on. Several different frontends may serve the same user in different transactions. The UDM-FEaccesses subscription information stored in the UDR and performsauthentication credential processing; user identification handling;access authorization; registration/mobility management; and subscriptionmanagement. The UDR may interact with PCF 1022. UDM 1024 may alsosupport SMS management, wherein an SMS-FE implements the similarapplication logic as discussed previously.

The AF 1026 may provide application influence on traffic routing, accessto the Network Capability Exposure (NCE), and interact with the policyframework for policy control. The NCE may be a mechanism that allows the5GC and AF 1026 to provide information to each other via NEF 1016, whichmay be used for edge computing implementations. In such implementations,the network operator and third party services may be hosted close to theUE 1002 access point of attachment to achieve an efficient servicedelivery through the reduced end-to-end latency and load on thetransport network. For edge computing implementations, the 5GC mayselect a UPF 1004 close to the UE 1002 and execute traffic steering fromthe UPF 1004 to DN 1006 via the N6 interface. This may be based on theUE subscription data, UE location, and information provided by the AF1026. In this way, the AF 1026 may influence UPF (re)selection andtraffic routing. Based on operator deployment, when AF 1026 isconsidered to be a trusted entity, the network operator may permit AF1026 to interact directly with relevant NFs.

As discussed previously, the CN 1010 may include an SMSF, which may beresponsible for SMS subscription checking and verification, and relayingSM messages to/from the UE 1002 to/from other entities, such as anSMS-GMSC/IWMSC/SMS-router. The SMS may also interact with AMF 1012 andUDM 1024 for notification procedure that the UE 1002 is available forSMS transfer (e.g., set a UE not reachable flag, and notifying UDM 1024when UE 1002 is available for SMS).

The system 1000 may include the following service-based interfaces:Namf: Service-based interface exhibited by AMF; Nsmf: Service-basedinterface exhibited by SMF; Nnef: Service-based interface exhibited byNEF; Npcf: Service-based interface exhibited by PCF; Nudm: Service-basedinterface exhibited by UDM; Naf: Service-based interface exhibited byAF; Nnrf: Service-based interface exhibited by NRF; and Nausf:Service-based interface exhibited by AUSF.

The system 1000 may include the following reference points: N1:Reference point between the UE and the AMF; N2: Reference point betweenthe (R)AN and the AMF; N3: Reference point between the (R)AN and theUPF; N4: Reference point between the SMF and the UPF; and N6: Referencepoint between the UPF and a Data Network. There may be many morereference points and/or service-based interfaces between the NF servicesin the NFs, however, these interfaces and reference points have beenomitted for clarity. For example, an NS reference point may be betweenthe PCF and the AF; an N7 reference point may be between the PCF and theSMF; an N11 reference point between the AMF and SMF; etc. In someembodiments, the CN 1010 may include an Nx interface, which is aninter-CN interface between the MME (e.g., MME(s) 930) and the AMF 1012in order to enable interworking between CN 1010 and CN 928.

Although not shown by FIG. 10, the system 1000 may include multiple RANnodes (such as (R)AN node 1008) wherein an Xn interface is definedbetween two or more (R)AN node 1008 (e.g., gNBs and the like) thatconnecting to 5GC 410, between a (R)AN node 1008 (e.g., gNB) connectingto CN 1010 and an eNB (e.g., a macro RAN node 918 of FIG. 9), and/orbetween two eNBs connecting to CN 1010.

In some implementations, the Xn interface may include an Xn user plane(Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U mayprovide non-guaranteed delivery of user plane PDUs and support/providedata forwarding and flow control functionality. The Xn-C may providemanagement and error handling functionality, functionality to manage theXn-C interface; mobility support for UE 1002 in a connected mode (e.g.,CM-CONNECTED) including functionality to manage the UE mobility forconnected mode between one or more (R)AN node 1008. The mobility supportmay include context transfer from an old (source) serving (R)AN node1008 to new (target) serving (R)AN node 1008; and control of user planetunnels between old (source) serving (R)AN node 1008 to new (target)serving (R)AN node 1008.

A protocol stack of the Xn-U may include a transport network layer builton Internet Protocol (IP) transport layer, and a GTP-U layer on top of aUDP and/or IP layer(s) to carry user plane PDUs. The Xn-C protocol stackmay include an application layer signaling protocol (referred to as XnApplication Protocol (Xn-AP)) and a transport network layer that isbuilt on an SCTP layer. The SCTP layer may be on top of an IP layer. TheSCTP layer provides the guaranteed delivery of application layermessages. In the transport IP layer point-to-point transmission is usedto deliver the signaling PDUs. In other implementations, the Xn-Uprotocol stack and/or the Xn-C protocol stack may be same or similar tothe user plane and/or control plane protocol stack(s) shown anddescribed herein.

FIG. 11 illustrates example components of a device 1100 in accordancewith some embodiments. In some embodiments, the device 1100 may includeapplication circuitry 1102, baseband circuitry 1104, Radio Frequency(RF) circuitry (shown as RF circuitry 1120), front-end module (FEM)circuitry (shown as FEM circuitry 1130), one or more antennas 1132, andpower management circuitry (PMC) (shown as PMC 1134) coupled together atleast as shown. The components of the illustrated device 1100 may beincluded in a UE or a RAN node. In some embodiments, the device 1100 mayinclude fewer elements (e.g., a RAN node may not utilize applicationcircuitry 1102, and instead include a processor/controller to process IPdata received from an EPC). In some embodiments, the device 1100 mayinclude additional elements such as, for example, memory/storage,display, camera, sensor, or input/output (I/O) interface. In otherembodiments, the components described below may be included in more thanone device (e.g., said circuitries may be separately included in morethan one device for Cloud-RAN (C-RAN) implementations).

The application circuitry 1102 may include one or more applicationprocessors. For example, the application circuitry 1102 may includecircuitry such as, but not limited to, one or more single-core ormulti-core processors. The processor(s) may include any combination ofgeneral-purpose processors and dedicated processors (e.g., graphicsprocessors, application processors, etc.). The processors may be coupledwith or may include memory/storage and may be configured to executeinstructions stored in the memory/storage to enable various applicationsor operating systems to run on the device 1100. In some embodiments,processors of application circuitry 1102 may process IP data packetsreceived from an EPC.

The baseband circuitry 1104 may include circuitry such as, but notlimited to, one or more single-core or multi-core processors. Thebaseband circuitry 1104 may include one or more baseband processors orcontrol logic to process baseband signals received from a receive signalpath of the RF circuitry 1120 and to generate baseband signals for atransmit signal path of the RF circuitry 1120. The baseband circuitry1104 may interface with the application circuitry 1102 for generationand processing of the baseband signals and for controlling operations ofthe RF circuitry 1120. For example, in some embodiments, the basebandcircuitry 1104 may include a third generation (3G) baseband processor(3G baseband processor 1106), a fourth generation (4G) basebandprocessor (4G baseband processor 1108), a fifth generation (5G) basebandprocessor (5G baseband processor 1110), or other baseband processor(s)1112 for other existing generations, generations in development or to bedeveloped in the future (e.g., second generation (2G), sixth generation(6G), etc.). The baseband circuitry 1104 (e.g., one or more of basebandprocessors) may handle various radio control functions that enablecommunication with one or more radio networks via the RF circuitry 1120.In other embodiments, some or all of the functionality of theillustrated baseband processors may be included in modules stored in thememory 1118 and executed via a Central Processing Unit (CPU 1114). Theradio control functions may include, but are not limited to, signalmodulation/demodulation, encoding/decoding, radio frequency shifting,etc. In some embodiments, modulation/demodulation circuitry of thebaseband circuitry 1104 may include Fast-Fourier Transform (FFT),precoding, or constellation mapping/demapping functionality. In someembodiments, encoding/decoding circuitry of the baseband circuitry 1104may include convolution, tail-biting convolution, turbo, Viterbi, or LowDensity Parity Check (LDPC) encoder/decoder functionality. Embodimentsof modulation/demodulation and encoder/decoder functionality are notlimited to these examples and may include other suitable functionalityin other embodiments.

In some embodiments, the baseband circuitry 1104 may include a digitalsignal processor (DSP), such as one or more audio DSP(s) 1116. The oneor more audio DSP(s) 1116 may be include elements forcompression/decompression and echo cancellation and may include othersuitable processing elements in other embodiments. Components of thebaseband circuitry may be suitably combined in a single chip, a singlechipset, or disposed on a same circuit board in some embodiments. Insome embodiments, some or all of the constituent components of thebaseband circuitry 1104 and the application circuitry 1102 may beimplemented together such as, for example, on a system on a chip (SOC).

In some embodiments, the baseband circuitry 1104 may provide forcommunication compatible with one or more radio technologies. Forexample, in some embodiments, the baseband circuitry 1104 may supportcommunication with an evolved universal terrestrial radio access network(EUTRAN) or other wireless metropolitan area networks (WMAN), a wirelesslocal area network (WLAN), or a wireless personal area network (WPAN).Embodiments in which the baseband circuitry 1104 is configured tosupport radio communications of more than one wireless protocol may bereferred to as multi-mode baseband circuitry.

The RF circuitry 1120 may enable communication with wireless networksusing modulated electromagnetic radiation through a non-solid medium. Invarious embodiments, the RF circuitry 1120 may include switches,filters, amplifiers, etc. to facilitate the communication with thewireless network. The RF circuitry 1120 may include a receive signalpath which may include circuitry to down-convert RF signals receivedfrom the FEM circuitry 1130 and provide baseband signals to the basebandcircuitry 1104. The RF circuitry 1120 may also include a transmit signalpath which may include circuitry to up-convert baseband signals providedby the baseband circuitry 1104 and provide RF output signals to the FEMcircuitry 1130 for transmission.

In some embodiments, the receive signal path of the RF circuitry 1120may include mixer circuitry 1122, amplifier circuitry 1124 and filtercircuitry 1126. In some embodiments, the transmit signal path of the RFcircuitry 1120 may include filter circuitry 1126 and mixer circuitry1122. The RF circuitry 1120 may also include synthesizer circuitry 1128for synthesizing a frequency for use by the mixer circuitry 1122 of thereceive signal path and the transmit signal path. In some embodiments,the mixer circuitry 1122 of the receive signal path may be configured todown-convert RF signals received from the FEM circuitry 1130 based onthe synthesized frequency provided by synthesizer circuitry 1128. Theamplifier circuitry 1124 may be configured to amplify the down-convertedsignals and the filter circuitry 1126 may be a low-pass filter (LPF) orband-pass filter (BPF) configured to remove unwanted signals from thedown-converted signals to generate output baseband signals. Outputbaseband signals may be provided to the baseband circuitry 1104 forfurther processing. In some embodiments, the output baseband signals maybe zero-frequency baseband signals, although this is not a requirement.In some embodiments, the mixer circuitry 1122 of the receive signal pathmay comprise passive mixers, although the scope of the embodiments isnot limited in this respect.

In some embodiments, the mixer circuitry 1122 of the transmit signalpath may be configured to up-convert input baseband signals based on thesynthesized frequency provided by the synthesizer circuitry 1128 togenerate RF output signals for the FEM circuitry 1130. The basebandsignals may be provided by the baseband circuitry 1104 and may befiltered by the filter circuitry 1126.

In some embodiments, the mixer circuitry 1122 of the receive signal pathand the mixer circuitry 1122 of the transmit signal path may include twoor more mixers and may be arranged for quadrature downconversion andupconversion, respectively. In some embodiments, the mixer circuitry1122 of the receive signal path and the mixer circuitry 1122 of thetransmit signal path may include two or more mixers and may be arrangedfor image rejection (e.g., Hartley image rejection). In someembodiments, the mixer circuitry 1122 of the receive signal path and themixer circuitry 1122 may be arranged for direct downconversion anddirect upconversion, respectively. In some embodiments, the mixercircuitry 1122 of the receive signal path and the mixer circuitry 1122of the transmit signal path may be configured for super-heterodyneoperation.

In some embodiments, the output baseband signals and the input basebandsignals may be analog baseband signals, although the scope of theembodiments is not limited in this respect. In some alternateembodiments, the output baseband signals and the input baseband signalsmay be digital baseband signals. In these alternate embodiments, the RFcircuitry 1120 may include analog-to-digital converter (ADC) anddigital-to-analog converter (DAC) circuitry and the baseband circuitry1104 may include a digital baseband interface to communicate with the RFcircuitry 1120.

In some dual-mode embodiments, a separate radio IC circuitry may beprovided for processing signals for each spectrum, although the scope ofthe embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 1128 may be afractional-N synthesizer or a fractional N/N+1 synthesizer, although thescope of the embodiments is not limited in this respect as other typesof frequency synthesizers may be suitable. For example, synthesizercircuitry 1128 may be a delta-sigma synthesizer, a frequency multiplier,or a synthesizer comprising a phase-locked loop with a frequencydivider.

The synthesizer circuitry 1128 may be configured to synthesize an outputfrequency for use by the mixer circuitry 1122 of the RF circuitry 1120based on a frequency input and a divider control input. In someembodiments, the synthesizer circuitry 1128 may be a fractional N/N+1synthesizer.

In some embodiments, frequency input may be provided by a voltagecontrolled oscillator (VCO), although that is not a requirement. Dividercontrol input may be provided by either the baseband circuitry 1104 orthe application circuitry 1102 (such as an applications processor)depending on the desired output frequency. In some embodiments, adivider control input (e.g., N) may be determined from a look-up tablebased on a channel indicated by the application circuitry 1102.

Synthesizer circuitry 1128 of the RF circuitry 1120 may include adivider, a delay-locked loop (DLL), a multiplexer and a phaseaccumulator. In some embodiments, the divider may be a dual modulusdivider (DMD) and the phase accumulator may be a digital phaseaccumulator (DPA). In some embodiments, the DMD may be configured todivide the input signal by either N or N+1 (e.g., based on a carry out)to provide a fractional division ratio. In some example embodiments, theDLL may include a set of cascaded, tunable, delay elements, a phasedetector, a charge pump and a D-type flip-flop. In these embodiments,the delay elements may be configured to break a VCO period up into Ndequal packets of phase, where Nd is the number of delay elements in thedelay line. In this way, the DLL provides negative feedback to helpensure that the total delay through the delay line is one VCO cycle.

In some embodiments, the synthesizer circuitry 1128 may be configured togenerate a carrier frequency as the output frequency, while in otherembodiments, the output frequency may be a multiple of the carrierfrequency (e.g., twice the carrier frequency, four times the carrierfrequency) and used in conjunction with quadrature generator and dividercircuitry to generate multiple signals at the carrier frequency withmultiple different phases with respect to each other. In someembodiments, the output frequency may be a LO frequency (fLO). In someembodiments, the RF circuitry 1120 may include an IQ/polar converter.

The FEM circuitry 1130 may include a receive signal path which mayinclude circuitry configured to operate on RF signals received from oneor more antennas 1132, amplify the received signals and provide theamplified versions of the received signals to the RF circuitry 1120 forfurther processing. The FEM circuitry 1130 may also include a transmitsignal path which may include circuitry configured to amplify signalsfor transmission provided by the RF circuitry 1120 for transmission byone or more of the one or more antennas 1132. In various embodiments,the amplification through the transmit or receive signal paths may bedone solely in the RF circuitry 1120, solely in the FEM circuitry 1130,or in both the RF circuitry 1120 and the FEM circuitry 1130.

In some embodiments, the FEM circuitry 1130 may include a TX/RX switchto switch between transmit mode and receive mode operation. The FEMcircuitry 1130 may include a receive signal path and a transmit signalpath. The receive signal path of the FEM circuitry 1130 may include anLNA to amplify received RF signals and provide the amplified received RFsignals as an output (e.g., to the RF circuitry 1120). The transmitsignal path of the FEM circuitry 1130 may include a power amplifier (PA)to amplify input RF signals (e.g., provided by the RF circuitry 1120),and one or more filters to generate RF signals for subsequenttransmission (e.g., by one or more of the one or more antennas 1132).

In some embodiments, the PMC 1134 may manage power provided to thebaseband circuitry 1104. In particular, the PMC 1134 may controlpower-source selection, voltage scaling, battery charging, or DC-to-DCconversion. The PMC 1134 may often be included when the device 1100 iscapable of being powered by a battery, for example, when the device 1100is included in a UE. The PMC 1134 may increase the power conversionefficiency while providing desirable implementation size and heatdissipation characteristics.

FIG. 11 shows the PMC 1134 coupled only with the baseband circuitry1104. However, in other embodiments, the PMC 1134 may be additionally oralternatively coupled with, and perform similar power managementoperations for, other components such as, but not limited to, theapplication circuitry 1102, the RF circuitry 1120, or the FEM circuitry1130.

In some embodiments, the PMC 1134 may control, or otherwise be part of,various power saving mechanisms of the device 1100. For example, if thedevice 1100 is in an RRC_Connected state, where it is still connected tothe RAN node as it expects to receive traffic shortly, then it may entera state known as Discontinuous Reception Mode (DRX) after a period ofinactivity. During this state, the device 1100 may power down for briefintervals of time and thus save power.

If there is no data traffic activity for an extended period of time,then the device 1100 may transition off to an RRC_Idle state, where itdisconnects from the network and does not perform operations such aschannel quality feedback, handover, etc. The device 1100 goes into avery low power state and it performs paging where again it periodicallywakes up to listen to the network and then powers down again. The device1100 may not receive data in this state, and in order to receive data,it transitions back to an RRC_Connected state.

An additional power saving mode may allow a device to be unavailable tothe network for periods longer than a paging interval (ranging fromseconds to a few hours). During this time, the device is totallyunreachable to the network and may power down completely. Any data sentduring this time incurs a large delay and it is assumed the delay isacceptable.

Processors of the application circuitry 1102 and processors of thebaseband circuitry 1104 may be used to execute elements of one or moreinstances of a protocol stack. For example, processors of the basebandcircuitry 1104, alone or in combination, may be used to execute Layer 3,Layer 2, or Layer 1 functionality, while processors of the applicationcircuitry 1102 may utilize data (e.g., packet data) received from theselayers and further execute Layer 4 functionality (e.g., transmissioncommunication protocol (TCP) and user datagram protocol (UDP) layers).As referred to herein, Layer 3 may comprise a radio resource control(RRC) layer, described in further detail below. As referred to herein,Layer 2 may comprise a medium access control (MAC) layer, a radio linkcontrol (RLC) layer, and a packet data convergence protocol (PDCP)layer, described in further detail below. As referred to herein, Layer 1may comprise a physical (PHY) layer of a UE/RAN node, described infurther detail below.

FIG. 12 illustrates example interfaces 1200 of baseband circuitry inaccordance with some embodiments. As discussed above, the basebandcircuitry 1104 of FIG. 11 may comprise 3G baseband processor 1106, 4Gbaseband processor 1108, 5G baseband processor 1110, other basebandprocessor(s) 1112, CPU 1114, and a memory 1118 utilized by saidprocessors. As illustrated, each of the processors may include arespective memory interface 1202 to send/receive data to/from the memory1118.

The baseband circuitry 1104 may further include one or more interfacesto communicatively couple to other circuitries/devices, such as a memoryinterface 1204 (e.g., an interface to send/receive data to/from memoryexternal to the baseband circuitry 1104), an application circuitryinterface 1206 (e.g., an interface to send/receive data to/from theapplication circuitry 1102 of FIG. 11), an RF circuitry interface 1208(e.g., an interface to send/receive data to/from RF circuitry 1120 ofFIG. 11), a wireless hardware connectivity interface 1210 (e.g., aninterface to send/receive data to/from Near Field Communication (NFC)components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi®components, and other communication components), and a power managementinterface 1212 (e.g., an interface to send/receive power or controlsignals to/from the PMC 1134.

FIG. 13 is an illustration of a control plane protocol stack inaccordance with some embodiments. In this embodiment, a control plane1300 is shown as a communications protocol stack between the UE 902 (oralternatively, the UE 904), the RAN 906 (e.g., the macro RAN node 918and/or the LP RAN node 920), and the MME(s) 930.

A PHY layer 1302 may transmit or receive information used by the MAClayer 1304 over one or more air interfaces. The PHY layer 1302 mayfurther perform link adaptation or adaptive modulation and coding (AMC),power control, cell search (e.g., for initial synchronization andhandover purposes), and other measurements used by higher layers, suchas an RRC layer 1310. The PHY layer 1302 may still further perform errordetection on the transport channels, forward error correction (FEC)coding/decoding of the transport channels, modulation/demodulation ofphysical channels, interleaving, rate matching, mapping onto physicalchannels, and Multiple Input Multiple Output (MIMO) antenna processing.

The MAC layer 1304 may perform mapping between logical channels andtransport channels, multiplexing of MAC service data units (SDUs) fromone or more logical channels onto transport blocks (TB) to be deliveredto PHY via transport channels, de-multiplexing MAC SDUs to one or morelogical channels from transport blocks (TB) delivered from the PHY viatransport channels, multiplexing MAC SDUs onto TBs, schedulinginformation reporting, error correction through hybrid automatic repeatrequest (HARQ), and logical channel prioritization.

An RLC layer 1306 may operate in a plurality of modes of operation,including: Transparent Mode (TM), Unacknowledged Mode (UM), andAcknowledged Mode (AM). The RLC layer 1306 may execute transfer of upperlayer protocol data units (PDUs), error correction through automaticrepeat request (ARQ) for AM data transfers, and concatenation,segmentation and reassembly of RLC SDUs for UM and AM data transfers.The RLC layer 1306 may also execute re-segmentation of RLC data PDUs forAM data transfers, reorder RLC data PDUs for UM and AM data transfers,detect duplicate data for UM and AM data transfers, discard RLC SDUs forUM and AM data transfers, detect protocol errors for AM data transfers,and perform RLC re-establishment.

A PDCP layer 1308 may execute header compression and decompression of IPdata, maintain PDCP Sequence Numbers (SNs), perform in-sequence deliveryof upper layer PDUs at re-establishment of lower layers, eliminateduplicates of lower layer SDUs at re-establishment of lower layers forradio bearers mapped on RLC AM, cipher and decipher control plane data,perform integrity protection and integrity verification of control planedata, control timer-based discard of data, and perform securityoperations (e.g., ciphering, deciphering, integrity protection,integrity verification, etc.).

The main services and functions of the RRC layer 1310 may includebroadcast of system information (e.g., included in Master InformationBlocks (MIBs) or System Information Blocks (SIBS) related to thenon-access stratum (NAS)), broadcast of system information related tothe access stratum (AS), paging, establishment, maintenance and releaseof an RRC connection between the UE and E-UTRAN (e.g., RRC connectionpaging, RRC connection establishment, RRC connection modification, andRRC connection release), establishment, configuration, maintenance andrelease of point-to-point radio bearers, security functions includingkey management, inter radio access technology (RAT) mobility, andmeasurement configuration for UE measurement reporting. Said MIBs andSIBs may comprise one or more information elements (IEs), which may eachcomprise individual data fields or data structures.

The UE 902 and the RAN 906 may utilize a Uu interface (e.g., an LTE-Uuinterface) to exchange control plane data via a protocol stackcomprising the PHY layer 1302, the MAC layer 1304, the RLC layer 1306,the PDCP layer 1308, and the RRC layer 1310.

In the embodiment shown, the non-access stratum (NAS) protocols (NASprotocols 1312) form the highest stratum of the control plane betweenthe UE 902 and the MME(s) 930. The NAS protocols 1312 support themobility of the UE 902 and the session management procedures toestablish and maintain IP connectivity between the UE 902 and the P-GW934.

The S1 Application Protocol (S1-AP) layer (S1-AP layer 1322) may supportthe functions of the S1 interface and comprise Elementary Procedures(EPs). An EP is a unit of interaction between the RAN 906 and the CN928. The S1-AP layer services may comprise two groups: UE-associatedservices and non UE-associated services. These services performfunctions including, but not limited to: E-UTRAN Radio Access Bearer(E-RAB) management, UE capability indication, mobility, NAS signalingtransport, RAN Information Management (RIM), and configuration transfer.

The Stream Control Transmission Protocol (SCTP) layer (alternativelyreferred to as the stream control transmission protocol/internetprotocol (SCTP/IP) layer) (SCTP layer 1320) may ensure reliable deliveryof signaling messages between the RAN 906 and the MME(s) 930 based, inpart, on the IP protocol, supported by an IP layer 1318. An L2 layer1316 and an L1 layer 1314 may refer to communication links (e.g., wiredor wireless) used by the RAN node and the MME to exchange information.

The RAN 906 and the MME(s) 930 may utilize an S1-MME interface toexchange control plane data via a protocol stack comprising the L1 layer1314, the L2 layer 1316, the IP layer 1318, the SCTP layer 1320, and theS1-AP layer 1322.

FIG. 14 is an illustration of a user plane protocol stack in accordancewith some embodiments. In this embodiment, a user plane 1400 is shown asa communications protocol stack between the UE 902 (or alternatively,the UE 904), the RAN 906 (e.g., the macro RAN node 918 and/or the LP RANnode 920), the S-GW 932, and the P-GW 934. The user plane 1400 mayutilize at least some of the same protocol layers as the control plane1300. For example, the UE 902 and the RAN 906 may utilize a Uu interface(e.g., an LTE-Uu interface) to exchange user plane data via a protocolstack comprising the PHY layer 1302, the MAC layer 1304, the RLC layer1306, the PDCP layer 1308.

The General Packet Radio Service (GPRS) Tunneling Protocol for the userplane (GTP-U) layer (GTP-U layer 1404) may be used for carrying userdata within the GPRS core network and between the radio access networkand the core network. The user data transported can be packets in any ofIPv4, IPv6, or PPP formats, for example. The UDP and IP security(UDP/IP) layer (UDP/IP layer 1402) may provide checksums for dataintegrity, port numbers for addressing different functions at the sourceand destination, and encryption and authentication on the selected dataflows. The RAN 906 and the S-GW 932 may utilize an S1-U interface toexchange user plane data via a protocol stack comprising the L1 layer1314, the L2 layer 1316, the UDP/IP layer 1402, and the GTP-U layer1404. The S-GW 932 and the P-GW 934 may utilize an S5/S8a interface toexchange user plane data via a protocol stack comprising the L1 layer1314, the L2 layer 1316, the UDP/IP layer 1402, and the GTP-U layer1404. As discussed above with respect to FIG. 13, NAS protocols supportthe mobility of the UE 902 and the session management procedures toestablish and maintain IP connectivity between the UE 902 and the P-GW934.

FIG. 15 illustrates components 1500 of a core network in accordance withsome embodiments. The components of the CN 928 may be implemented in onephysical node or separate physical nodes including components to readand execute instructions from a machine-readable or computer-readablemedium (e.g., a non-transitory machine-readable storage medium). In someembodiments, Network Functions Virtualization (NFV) is utilized tovirtualize any or all of the above described network node functions viaexecutable instructions stored in one or more computer readable storagemediums (described in further detail below). A logical instantiation ofthe CN 928 may be referred to as a network slice 1502 (e.g., the networkslice 1502 is shown to include the HSS 936, the MME(s) 930, and the S-GW932). A logical instantiation of a portion of the CN 928 may be referredto as a network sub-slice 1504 (e.g., the network sub-slice 1504 isshown to include the P-GW 934 and the PCRF 940).

NFV architectures and infrastructures may be used to virtualize one ormore network functions, alternatively performed by proprietary hardware,onto physical resources comprising a combination of industry-standardserver hardware, storage hardware, or switches. In other words, NFVsystems can be used to execute virtual or reconfigurable implementationsof one or more EPC components/functions.

FIG. 16 is a block diagram illustrating components, according to someexample embodiments, of a system 1600 to support NFV. The system 1600 isillustrated as including a virtualized infrastructure manager (shown asVIM 1602), a network function virtualization infrastructure (shown asNFVI 1604), a VNF manager (shown as VNFM 1606), virtualized networkfunctions (shown as VNF 1608), an element manager (shown as EM 1610), anNFV Orchestrator (shown as NFVO 1612), and a network manager (shown asNM 1614).

The VIM 1602 manages the resources of the NFVI 1604. The NFVI 1604 caninclude physical or virtual resources and applications (includinghypervisors) used to execute the system 1600. The VIM 1602 may managethe life cycle of virtual resources with the NFVI 1604 (e.g., creation,maintenance, and tear down of virtual machines (VMs) associated with oneor more physical resources), track VM instances, track performance,fault and security of VM instances and associated physical resources,and expose VM instances and associated physical resources to othermanagement systems.

The VNFM 1606 may manage the VNF 1608. The VNF 1608 may be used toexecute EPC components/functions. The VNFM 1606 may manage the lifecycle of the VNF 1608 and track performance, fault and security of thevirtual aspects of VNF 1608. The EM 1610 may track the performance,fault and security of the functional aspects of VNF 1608. The trackingdata from the VNFM 1606 and the EM 1610 may comprise, for example,performance measurement (PM) data used by the VIM 1602 or the NFVI 1604.Both the VNFM 1606 and the EM 1610 can scale up/down the quantity ofVNFs of the system 1600.

The NFVO 1612 may coordinate, authorize, release and engage resources ofthe NFVI 1604 in order to provide the requested service (e.g., toexecute an EPC function, component, or slice). The NM 1614 may provide apackage of end-user functions with the responsibility for the managementof a network, which may include network elements with VNFs,non-virtualized network functions, or both (management of the VNFs mayoccur via the EM 1610).

FIG. 17 is a block diagram illustrating components 1700, according tosome example embodiments, able to read instructions from amachine-readable or computer-readable medium (e.g., a non-transitorymachine-readable storage medium) and perform any one or more of themethodologies discussed herein. Specifically, FIG. 17 shows adiagrammatic representation of hardware resources 1702 including one ormore processors 1712 (or processor cores), one or more memory/storagedevices 1718, and one or more communication resources 1720, each ofwhich may be communicatively coupled via a bus 1722. For embodimentswhere node virtualization (e.g., NFV) is utilized, a hypervisor 1704 maybe executed to provide an execution environment for one or more networkslices/sub-slices to utilize the hardware resources 1702.

The processors 1712 (e.g., a central processing unit (CPU), a reducedinstruction set computing (RISC) processor, a complex instruction setcomputing (CISC) processor, a graphics processing unit (GPU), a digitalsignal processor (DSP) such as a baseband processor, an applicationspecific integrated circuit (ASIC), a radio-frequency integrated circuit(RFIC), another processor, or any suitable combination thereof) mayinclude, for example, a processor 1714 and a processor 1716.

The memory/storage devices 1718 may include main memory, disk storage,or any suitable combination thereof. The memory/storage devices 1718 mayinclude, but are not limited to any type of volatile or non-volatilememory such as dynamic random access memory (DRAM), static random-accessmemory (SRAM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), Flashmemory, solid-state storage, etc.

The communication resources 1720 may include interconnection or networkinterface components or other suitable devices to communicate with oneor more peripheral devices 1706 or one or more databases 1708 via anetwork 1710. For example, the communication resources 1720 may includewired communication components (e.g., for coupling via a UniversalSerial Bus (USB)), cellular communication components, NFC components,Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components,and other communication components.

Instructions 1724 may comprise software, a program, an application, anapplet, an app, or other executable code for causing at least any of theprocessors 1712 to perform any one or more of the methodologiesdiscussed herein. The instructions 1724 may reside, completely orpartially, within at least one of the processors 1712 (e.g., within theprocessor's cache memory), the memory/storage devices 1718, or anysuitable combination thereof. Furthermore, any portion of theinstructions 1724 may be transferred to the hardware resources 1702 fromany combination of the peripheral devices 1706 or the databases 1708.Accordingly, the memory of the processors 1712, the memory/storagedevices 1718, the peripheral devices 1706, and the databases 1708 areexamples of computer-readable and machine-readable media.

Interworking with EPC

A 5G System may interwork with a 4G EPC system either throughsingle-registration or dual-registration mode. If RDS is supported inboth 5G System and 4G System then PDU sessions or PDN connections withRDS capability may be transferred from 5G system to 4G system and viceversa. The UE has to setup the RDS transfers for each PDN connection inthe target system. On transferring a PDU session from 5GS to 4GS, theEPC will map the NEF address to equivalent SCEF ID and the correspondingSCS/AS and the UE will negotiate the support for RDS in system andestablish a PDN connection with the corresponding SCEF. If the NEFaddress cannot be mapped to SCEF ID or the corresponding SCS/AS cannotbe located, or the PDN connection with appropriate SCEF cannot beestablished, then the RDS capability will not be supported in 4GS. TheUE may continue to use the same port numbers as in 5GS in 4GS as well,if they are available, else new port numbers may be allocated in 4GS andthe RDS connection established.

The following examples pertain to further embodiments.

Example 1A may include a 5G system comprising: gNB, AMF, SMF, UPF, NEF,UDM, NSSF, AUSF, AF, AS and other elements as described in 3GPP TS23.501 and 3GPP TS 24.501.

Example 2A may include the 5G system of Example 1A and/or some otherExamples herein, further comprising a UE, wherein the UE performsReliable Data Transfer between UE and NEF using the RDS protocol asdescribed in TS 24.250. The communication between UE and NEF isbidirectional and supports both MO/MT data delivery in roaming andnon-roaming scenarios.

Example 3A may include the 5G system of Example 2A and/or some otherExamples herein, wherein the communication between UE and NEF can beperformed over both 3GPP and non-3GPP accesses.

Example 4A may include the 5G system of Example 2A and/or some otherExamples herein, wherein the UE discovers support for RDS with NEFduring the Registration procedure. The UE specifies “RDS Supported”indication over non-3GPP and 3GPP accesses in REGISTRATION_REQUESTmessage. The network responds with “RDS Supported” or no supportindication in REGISTRATION_ACCEPT/REGISTRATION_REJECT message.

Example 5A may include the 5G system of Example 4A and/or some otherExamples herein, wherein the AMF discovers the NEF address either basedon pre-configuration (i.e., NEF FQDN); or the NEF address is receivedfrom the UDM; or the AMF invokes Nnrf_NFDiscovery service operation fromNRF to discover the NEF address as described in clause 5.2.7.3.2 of TS23.502.

Example 6A may include the 5G system of Example 5A and/or some otherExamples herein, wherein the AMF uses the discovered NEf address andinvokes Nnef_RDS_Activate service from the NEF including AMF address,Access Type, GPSI (if available) and SUPI. The NEF retrieves UEsubscription data from UDM and creates UE context to store RDSconfiguration information.

Example 7A may include the 5G system of Example 5A and/or some otherExamples herein, wherein the AF/AS establishes RDS configuration withthe NEF using the Nnref_RDS_Config_Request service operation toestablish routing information in NEF. The AF/AS provides externalidentifier for UE message and reliable data service configurationinformation (e.g. application port number, acknowledged orunacknowledged transfer, etc.) to the NEF.

Example 8A may include the 5G system of Example 7A and/or some otherExamples herein, wherein the NEF uses Nnref_RDS_Config_Response serviceoperation to acknowledge acceptance of the RDS Configuration Request tothe AF/AS. If the RDS Configuration was accepted, the NEF will create anassociation between the External Identifier and SUPI in UE context. Inthe MT reliable small data delivery procedure, the NEF will use ExternalIdentifier to determine the SUPI and receiver port number. In the MOreliable small data delivery procedure, the NEF will use the SUPI, todetermine AS/AF address and application port number from the UE context.

Example 9A may include the 5G system of Example 8A and/or some otherExamples herein, wherein RDS packets are transmitted over NAS withoutthe need to establish data radio bearers, i.e. via NAS transportmessage, which can carry RDS payload. UE and Network supports RDSprotocol as specified in TS 24.250.

Example 10A may include a 4G system comprising of MME, P-GW, SCEF, S-GW,HSS, etc. as described in TS 23.401.

Example 11A may include a 5G system of Example 9A and/or some otherExamples herein, and a 4G system of Example 10A and/or some otherExamples herein, wherein the UE that supports interworking between 4Gand 5G system and performs migration from 5GS to 4GS. If a PDU sessionsupports RDS configuration in 5GS and if the UE interworks and migratesto 4G system that supports RDS configuration, then the corresponding PDNconnection in 4G system will also support RDS. The same will also holdtrue in other direction.

Example 12A may include an apparatus comprising means to perform one ormore elements of a method described in or related to any of Examples1A-11A, or any other method or process described herein.

Example 13A may include one or more non-transitory computer-readablemedia comprising instructions to cause an electronic device, uponexecution of the instructions by one or more processors of theelectronic device, to perform one or more elements of a method describedin or related to any of Examples 1A-11A, or any other method or processdescribed herein.

Example 14A may include an apparatus comprising logic, modules, orcircuitry to perform one or more elements of a method described in orrelated to any of Examples 1A-11A, or any other method or processdescribed herein.

Example 15A may include a method, technique, or process as described inor related to any of Examples 1A-11A, or portions or parts thereof.

Example 16A may include an apparatus comprising: one or more processorsand one or more computer readable media comprising instructions that,when executed by the one or more processors, cause the one or moreprocessors to perform the method, techniques, or process as described inor related to any of Examples 1A-11A, or portions thereof.

Example 17A may include a signal as described in or related to any ofExamples 1A-11A, or portions or parts thereof.

Example 18A may include a signal in a wireless network as shown anddescribed herein.

Example 19A may include a method of communicating in a wireless networkas shown and described herein.

Example 20A may include a system for providing wireless communication asshown and described herein.

Example 21A may include a device for providing wireless communication asshown and described herein.

Example 1B is a method for use by a user equipment (UE) to performreliable data service for unstructured protocol data unit (PDU)sessions. The method include indicating, to a mobile communicationnetwork, a capability of the UE to support a reliable data serviceprotocol. The method also includes processing an indication, from themobile communication network, that the reliable data service protocol issupported by the mobile communication network. The method furtherincludes cooperating with the mobile communication network to establisha PDU session between the UE as a first endpoint of the PDU session anda node or function in the mobile communication network as a secondendpoint of the PDU session, and processing non-access stratum (NAS)messages comprising a PDU session identifier (ID) and data tocommunicate between the first endpoint and the second endpoint. Whereinprocessing the NAS messages, for both mobile originated (MO) datatransfer and mobile terminated (MT) data transfer, comprises using thereliable data service protocol to determine whether PDUs of the NASmessages require no acknowledgement, require acknowledgment, or includean acknowledgement. Wherein processing the NAS messages furthercomprises using the reliable data service protocol to detect andeliminate duplicate PDUs received at the UE in the NAS messages.

Example 2B is the method of Example 1B, wherein using the reliable dataservice protocol further comprises processing packet headers todetermine whether the PDUs of the NAS messages require noacknowledgement, require acknowledgment, or include the acknowledgement.

Example 3B is the method of Example 2B, wherein using the reliable dataservice protocol further comprises processing port numbers in the packetheaders to identify applications on an originator and a receiver of theNAS messages.

Example 4B is the method of Example 1B, wherein the second endpoint ofthe PDU session comprises a network exposure function (NEF).

Example 5B is the method of Example 1B, wherein the second endpoint ofthe PDU session comprises a user plane function (UPF).

Example 6B is the method of Example 1B, wherein for the MO datatransfer, the method further comprises generating an initial NASmessage, for communication from the UE to an access and mobilitymanagement function (AMF) through an access node, the initial NASmessage comprising an integrity protected NAS PDU, the integrityprotected NAS PUD comprising the PDU session ID and uplink data aspayload.

Example 7B is the method of Example 6B, wherein the initial NAS messagefurther comprises release assistance information to indicate, to theAMF, whether the integrity protected NAS PDU is a last PDU expected soas to release a connection between the UE and the access node.

Example 8B is the method of Example 6B, further comprising processing adownlink NAS message received from the AMF comprising an acknowledgementthat the initial NAS message was received by the second endpoint of thePDU session.

Example 9B is the method of Example 8B, wherein the downlink NAS messagefurther comprises the PDU session ID.

Example 10B is the method of Example 1B, wherein for the MT datatransfer, the method further comprises processing a downlink NAS messagereceived from an access and mobility management function (AMF) throughan access node, the downlink NAS message comprising the PDU session IDand downlink data as payload.

Example 11B is the method of Example 10B, further comprising, inresponse to determining that a PDU header in the NAS message indicatesthat an acknowledgment is requested, generating an uplink NAS message tocommunicate from the UE to the AMF through the access node, wherein theuplink NAS message comprises the acknowledgment.

Example 12B is the method of Example 10B, wherein when the UE is in aconnection management (CM) idle state, before processing the downlinkNAS message, the method further comprises: processing a paging messagefrom the access node; and in response to the paging message, generatingan initial NAS message or service request to send to the AMF.

Example 13B is a method for a network exposure function (NEF) to providereliable non-internet protocol (IP) data delivery in a wireless network.The method includes: processing a configuration request, from anapplication function (AF), to configure non-IP data delivery, theconfiguration request including a user equipment (UE) identifier; inresponse to the configuration request, generating a unified datamanagement (UDM) request to determine whether the configuration requestfor the UE identifier is authorized; processing a UDM responseindicating authorization for non-IP data delivery, the UDM responsecomprising a subscription permanent identifier (SUPI) mapped to the UEidentifier; and in response to the UDM response: generating aconfiguration response to acknowledge acceptance of the configurationrequest to the AF; and creating an association between the UE identifierand the SUPI in a UE context.

Example 14B is the method of Example 13B, wherein the UE identifier isselected from a group comprising an external UE identifier and a generalpublic subscription identifier (GPSI).

Example 15B is the method of Example 13B, further comprising:cooperating with at least one of an access and mobility managementfunction (AMF) and a session management function (SMF) to establish anon-IP protocol data unit (PDU) session between the NEF and the UE; andmaintaining an association of at least a PDU session identifier, the UEidentifier, and the SUPI.

Example 16B is the method of Example 15B, further comprising, in amobile terminated (MT) procedure for non-IP data delivery, using atleast the UE identifier to determine the SUPI and a receiver portnumber.

Example 17B is the method of Example 16B, further comprising using atleast the UE identifier in the MT procedure to determine the PDU sessionidentifier.

Example 18B is the method of Example 15B, further comprising, in amobile originated (MO) procedure for non-IP data delivery, using theSUPI to determine at least one of an address corresponding to the AF andan application port number corresponding to the UE.

Example 19B is the method of Example 18B, further comprising using thePDU session identifier to at least one of the address corresponding tothe AF and the application port number corresponding to the UE.

Example 20B is a method for an access and mobility management function(AMF) to provide mobile originated (MO) data transport in acommunication network. The method includes: processing a non-accessstratum (NAS) message from a user equipment (UE), the NAS messagecomprising a protocol data unit (PDU) session identifier (ID) and uplinkdata; checking integrity of and decrypting the NAS message comprisingthe PDU session ID and the uplink data; determining, based on the PDUsession ID, a session management function (SMF); routing the PDU sessionID and the uplink data to the SMF for forwarding to a function in thecommunication network; and generating a downlink NAS transport messageto communicate to the UE, the downlink NAS transport message comprisingthe PDU session ID and downlink data provided from the function in thecommunication network through the SMF.

Example 21B is the method of Example 20B, further comprising, inresponse to an indication that the UE supports reliable data service(RDS), determining whether a header in the NAS message from the UEindicates a PDU of the NAS message requires no acknowledgement, requiresacknowledgment, or includes an acknowledgement of prior downlink data.

Example 22B is the method of Example 21B, wherein the downlink datacomprising an acknowledgement of the uplink data.

Example 23B is the method of Example 20B, wherein the function in thecommunication network comprises a network exposure function (NEF) or auser plane function (UPF).

Example 24B is the method of Example 20B, wherein the NAS message fromthe UE further comprises release assistance information indicatingwhether the NAS message comprises a last PDU expected, and wherein themethod further comprises releasing, based on the release assistanceinformation indicating that the NAS message comprises a last PDUexpected, a connection between the UE and an access node.

Example 25B is a method for an access and mobility management function(AMF) to provide mobile terminated (MT) data transport in acommunication network. The method includes: processing a non-accessstratum (NAS) message and a protocol data unit (PDU) session identifier(ID) from a session management function (SMF), the NAS messagecomprising downlink data from a function in the communication network;generating an integrity protected and encrypted downlink NAS transportmessage comprising the PDU session ID and the NAS message from the SMF;and forwarding the downlink NAS transport message to an access node fordelivery to a user equipment (UE) associated with the PDU session ID.

Example 26B is the method of Example 25B, wherein the PDU session is ofan unstructured type, reliable data service (RDS) is enabled, andwherein the downlink NAS transport message includes an indication thatRDS acknowledgement is requested.

Example 27B is the method of Example 26B, the method further comprisingprocessing an uplink NAS message from the UE, the uplink NAS messagecomprising an acknowledgement of the downlink data.

Example 28B is the method of Example 25B, wherein the function in thecommunication network comprises a network exposure function (NEF) or auser plane function (UPF).

Example 29B is the method of Example 25B, further comprising, in respondto determining that the UE is in a connection management (CM) idlestate, before forwarding the downlink NAS transport message to theaccess node for delivery to the UE, sending a paging message to theaccess node to perform paging of the UE.

Example 30B is a computing apparatus comprising a processor and a memorystoring instructions that, when executed by the processor, configure theapparatus to: indicate, to a mobile communication network, a capabilityof the UE to support a reliable data service protocol; process anindication, from the mobile communication network, that the reliabledata service protocol is supported by the mobile communication network;cooperate with the mobile communication network to establish a PDUsession between the UE as a first endpoint of the PDU session and a nodeor function in the mobile communication network as a second endpoint ofthe PDU session; and process non-access stratum (NAS) messagescomprising a PDU session identifier (ID) and data to communicate betweenthe first endpoint and the second endpoint, wherein processing the NASmessages, for both mobile originated (MO) data transfer and mobileterminated (MT) data transfer, comprises use the reliable data serviceprotocol to determine whether PDUs of the NAS messages require noacknowledgement, require acknowledgment, or include an acknowledgement,and wherein processing the NAS messages further comprises use thereliable data service protocol to detect and eliminate duplicate PDUsreceived at the UE in the NAS messages.

Example 31B is the computing apparatus of Example 30B, wherein using thereliable data service protocol further comprises process packet headersto determine whether the PDUs of the NAS messages require noacknowledgement, require acknowledgment, or include the acknowledgement.

Example 32B is the computing apparatus of Example 31B, wherein using thereliable data service protocol further comprises process port numbers inthe packet headers to identify applications on an originator and areceiver of the NAS messages.

Example 33B is the computing apparatus of Example 30B, wherein thesecond endpoint of the PDU session comprises a network exposure function(NEF).

Example 34B is the computing apparatus of Example 30B, wherein thesecond endpoint of the PDU session comprises a user plane function(UPF).

Example 35B is the computing apparatus of Example 30B, wherein for theMO data transfer, the method further comprises generate an initial NASmessage, for communication from the UE to an access and mobilitymanagement function (AMF) through an access node, the initial NASmessage comprising an integrity protected NAS PDU, the integrityprotected NAS PUD comprising the PDU session ID and uplink data aspayload.

Example 36B is the computing apparatus of Example 35B, wherein theinitial NAS message further comprises release assistance information toindicate, to the AMF, whether the integrity protected NAS PDU is a lastPDU expected so as to release a connection between the UE and the accessnode.

Example 37B is the computing apparatus of Example 35B, wherein theinstructions further configure the apparatus to process a downlink NASmessage received from the AMF comprising an acknowledgement that theinitial NAS message was received by the second endpoint of the PDUsession.

Example 38B is the computing apparatus of Example 37B, wherein thedownlink NAS message further comprises the PDU session ID.

Example 39B is the computing apparatus of Example 30B, wherein for theMT data transfer, the method further comprises process a downlink NASmessage received from an access and mobility management function (AMF)through an access node, the downlink NAS message comprising the PDUsession ID and downlink data as payload.

Example 40B is the computing apparatus of Example 39B, wherein theinstructions further configure the apparatus to, in response todetermining that a PDU header in the NAS message indicates that anacknowledgment is requested, generate an uplink NAS message tocommunicate from the UE to the AMF through the access node, wherein theuplink NAS message comprises the acknowledgment.

Example 41B is the computing apparatus of Example 39B, wherein when theUE is in a connection management (CM) idle state, before process thedownlink NAS message, the method further comprises: process a pagingmessage from the access node; and in response to the paging message,generating an initial NAS message or service request to send to the AMF.

Example 42B is a computing apparatus comprising: a processor and amemory storing instructions that, when executed by the processor,configure the apparatus to: process a configuration request, from anapplication function (AF), to configure non-IP data delivery, theconfiguration request including a user equipment (UE) identifier; inresponse to the configuration request, generating a unified datamanagement (UDM) request to determine whether the configuration requestfor the UE identifier is authorized; process a UDM response indicatingauthorization for non-IP data delivery, the UDM response comprising asubscription permanent identifier (SUPI) mapped to the UE identifier;and in response to the UDM response: generate a configuration responseto acknowledge acceptance of the configuration request to the AF; andcreate an association between the UE identifier and the SUPI in a UEcontext.

Example 43B is the computing apparatus of Example 42B, wherein the UEidentifier is selected from a group comprising an external UE identifierand a general public subscription identifier (GPSI).

Example 44B is the computing apparatus of Example 42B, wherein theinstructions further configure the apparatus to: cooperate with at leastone of an access and mobility management function (AMF) and a sessionmanagement function (SMF) to establish a non-IP protocol data unit (PDU)session between the NEF and the UE; and maintain an association of atleast a PDU session identifier, the UE identifier, and the SUPI.

Example 45B is the computing apparatus of Example 44B, wherein theinstructions further configure the apparatus to, in a mobile terminated(MT) procedure for non-IP data delivery, use at least the UE identifierto determine the SUPI and a receiver port number.

Example 46B is the computing apparatus of Example 45B, wherein theinstructions further configure the apparatus to use at least the UEidentifier in the MT procedure to determine the PDU session identifier.

Example 47B is the computing apparatus of Example 44B, wherein theinstructions further configure the apparatus to, in a mobile originated(MO) procedure for non-IP data delivery, use the SUPI to determine atleast one of an address corresponding to the AF and an application portnumber corresponding to the UE.

Example 48B is the computing apparatus of Example 47B, wherein theinstructions further configure the apparatus to use the PDU sessionidentifier to at least one of the address corresponding to the AF andthe application port number corresponding to the UE.

Example 49B is a non-transitory computer-readable storage medium, thecomputer-readable storage medium including instructions that whenexecuted by a computer, cause the computer to: process a non-accessstratum (NAS) message from a user equipment (UE), the NAS messagecomprising a protocol data unit (PDU) session identifier (ID) and uplinkdata; check integrity of and decrypting the NAS message comprising thePDU session ID and the uplink data; determine, based on the PDU sessionID, a session management function (SMF); rout the PDU session ID and theuplink data to the SMF for forwarding to a function in the communicationnetwork; and generate a downlink NAS transport message to communicate tothe UE, the downlink NAS transport message comprising the PDU session IDand downlink data provided from the function in the communicationnetwork through the SMF.

Example 50B is the computer-readable storage medium of Example 49B,wherein the instructions further configure the computer to, in responseto an indication that the UE supports reliable data service (RDS),determine whether a header in the NAS message from the UE indicates aPDU of the NAS message requires no acknowledgement, requiresacknowledgment, or includes an acknowledgement of prior downlink data.

Example 51B is the computer-readable storage medium of Example 50B,wherein the downlink data comprising an acknowledgement of the uplinkdata.

Example 52B is the computer-readable storage medium of Example 49B,wherein the function in the communication network comprises a networkexposure function (NEF) or a user plane function (UPF).

Example 53B is the computer-readable storage medium of Example 49B,wherein the NAS message from the UE further comprises release assistanceinformation indicate whether the NAS message comprises a last PDUexpected, and wherein the method further comprises releasing, based onthe release assistance information indicating that the NAS messagecomprises a last PDU expected, a connection between the UE and an accessnode.

Example 54B is a non-transitory computer-readable storage medium, thecomputer-readable storage medium including instructions that whenexecuted by a computer, cause the computer to: process a non-accessstratum (NAS) message and a protocol data unit (PDU) session identifier(ID) from a session management function (SMF), the NAS messagecomprising downlink data from a function in the communication network;generate an integrity protected and encrypted downlink NAS transportmessage comprising the PDU session ID and the NAS message from the SMF;and forward the downlink NAS transport message to an access node fordelivery to a user equipment (UE) associated with the PDU session ID.

Example 55B is the computer-readable storage medium of Example 54B,wherein the PDU session is of an unstructured type, reliable dataservice (RDS) is enabled, and wherein the downlink NAS transport messageincludes an indication that RDS acknowledgement is requested.

Example 56B is the computer-readable storage medium of Example 55B, themethod wherein the instructions further configure the computer toprocess an uplink NAS message from the UE, the uplink NAS messagecomprising an acknowledgement of the downlink data.

Example 57B is the computer-readable storage medium of Example 54B,wherein the function in the communication network comprises a networkexposure function (NEF) or a user plane function (UPF).

Example 58B is the computer-readable storage medium of Example 54B,wherein the instructions further configure the computer to, in respondto determining that the UE is in a connection management (CM) idlestate, before forward the downlink NAS transport message to the accessnode for delivery to the UE, sending a paging message to the access nodeto perform paging of the UE.

Example 59B is a computing apparatus including a processor and a memorystoring instructions that, when executed by the processor, configure theapparatus to perform the method of any one of Examples 1B-29B.

Example 60B is a non-transitory computer-readable storage mediumincluding instructions that, when processed by a computer, configure thecomputer to perform the method of any one of Examples 1B-29B.

Any of the above described examples may be combined with any otherexample (or combination of examples), unless explicitly statedotherwise. The foregoing description of one or more implementationsprovides illustration and description, but is not intended to beexhaustive or to limit the scope of embodiments to the precise formdisclosed. Modifications and variations are possible in light of theabove teachings or may be acquired from practice of various embodiments.

Embodiments and implementations of the systems and methods describedherein may include various operations, which may be embodied inmachine-executable instructions to be executed by a computer system. Acomputer system may include one or more general-purpose orspecial-purpose computers (or other electronic devices). The computersystem may include hardware components that include specific logic forperforming the operations or may include a combination of hardware,software, and/or firmware.

Computer systems and the computers in a computer system may be connectedvia a network. Suitable networks for configuration and/or use asdescribed herein include one or more local area networks, wide areanetworks, metropolitan area networks, and/or Internet or IP networks,such as the World Wide Web, a private Internet, a secure Internet, avalue-added network, a virtual private network, an extranet, anintranet, or even stand-alone machines which communicate with othermachines by physical transport of media. In particular, a suitablenetwork may be formed from parts or entireties of two or more othernetworks, including networks using disparate hardware and networkcommunication technologies.

One suitable network includes a server and one or more clients; othersuitable networks may include other combinations of servers, clients,and/or peer-to-peer nodes, and a given computer system may function bothas a client and as a server. Each network includes at least twocomputers or computer systems, such as the server and/or clients. Acomputer system may include a workstation, laptop computer,disconnectable mobile computer, server, mainframe, cluster, so-called“network computer” or “thin client,” tablet, smart phone, personaldigital assistant or other hand-held computing device, “smart” consumerelectronics device or appliance, medical device, or a combinationthereof.

Suitable networks may include communications or networking software,such as the software available from Novell®, Microsoft®, and othervendors, and may operate using TCP/IP, SPX, IPX, and other protocolsover twisted pair, coaxial, or optical fiber cables, telephone lines,radio waves, satellites, microwave relays, modulated AC power lines,physical media transfer, and/or other data transmission “wires” known tothose of skill in the art. The network may encompass smaller networksand/or be connectable to other networks through a gateway or similarmechanism.

Various techniques, or certain aspects or portions thereof, may take theform of program code (i.e., instructions) embodied in tangible media,such as floppy diskettes, CD-ROMs, hard drives, magnetic or opticalcards, solid-state memory devices, a nontransitory computer-readablestorage medium, or any other machine-readable storage medium wherein,when the program code is loaded into and executed by a machine, such asa computer, the machine becomes an apparatus for practicing the varioustechniques. In the case of program code execution on programmablecomputers, the computing device may include a processor, a storagemedium readable by the processor (including volatile and nonvolatilememory and/or storage elements), at least one input device, and at leastone output device. The volatile and nonvolatile memory and/or storageelements may be a RAM, an EPROM, a flash drive, an optical drive, amagnetic hard drive, or other medium for storing electronic data. TheeNB (or other base station) and UE (or other mobile station) may alsoinclude a transceiver component, a counter component, a processingcomponent, and/or a clock component or timer component. One or moreprograms that may implement or utilize the various techniques describedherein may use an application programming interface (API), reusablecontrols, and the like. Such programs may be implemented in a high-levelprocedural or an object-oriented programming language to communicatewith a computer system. However, the program(s) may be implemented inassembly or machine language, if desired. In any case, the language maybe a compiled or interpreted language, and combined with hardwareimplementations.

Each computer system includes one or more processors and/or memory;computer systems may also include various input devices and/or outputdevices. The processor may include a general purpose device, such as anIntel®, AMD®, or other “off-the-shelf” microprocessor. The processor mayinclude a special purpose processing device, such as ASIC, SoC, SiP,FPGA, PAL, PLA, FPLA, PLD, or other customized or programmable device.The memory may include static RAM, dynamic RAM, flash memory, one ormore flip-flops, ROM, CD-ROM, DVD, disk, tape, or magnetic, optical, orother computer storage medium. The input device(s) may include akeyboard, mouse, touch screen, light pen, tablet, microphone, sensor, orother hardware with accompanying firmware and/or software. The outputdevice(s) may include a monitor or other display, printer, speech ortext synthesizer, switch, signal line, or other hardware withaccompanying firmware and/or software.

It should be understood that many of the functional units described inthis specification may be implemented as one or more components, whichis a term used to more particularly emphasize their implementationindependence. For example, a component may be implemented as a hardwarecircuit comprising custom very large scale integration (VLSI) circuitsor gate arrays, or off-the-shelf semiconductors such as logic chips,transistors, or other discrete components. A component may also beimplemented in programmable hardware devices such as field programmablegate arrays, programmable array logic, programmable logic devices, orthe like.

Components may also be implemented in software for execution by varioustypes of processors. An identified component of executable code may, forinstance, comprise one or more physical or logical blocks of computerinstructions, which may, for instance, be organized as an object, aprocedure, or a function. Nevertheless, the executables of an identifiedcomponent need not be physically located together, but may comprisedisparate instructions stored in different locations that, when joinedlogically together, comprise the component and achieve the statedpurpose for the component.

Indeed, a component of executable code may be a single instruction, ormany instructions, and may even be distributed over several differentcode segments, among different programs, and across several memorydevices. Similarly, operational data may be identified and illustratedherein within components, and may be embodied in any suitable form andorganized within any suitable type of data structure. The operationaldata may be collected as a single data set, or may be distributed overdifferent locations including over different storage devices, and mayexist, at least partially, merely as electronic signals on a system ornetwork. The components may be passive or active, including agentsoperable to perform desired functions.

Several aspects of the embodiments described will be illustrated assoftware modules or components. As used herein, a software module orcomponent may include any type of computer instruction orcomputer-executable code located within a memory device. A softwaremodule may, for instance, include one or more physical or logical blocksof computer instructions, which may be organized as a routine, program,object, component, data structure, etc., that perform one or more tasksor implement particular data types. It is appreciated that a softwaremodule may be implemented in hardware and/or firmware instead of or inaddition to software. One or more of the functional modules describedherein may be separated into sub-modules and/or combined into a singleor smaller number of modules.

In certain embodiments, a particular software module may includedisparate instructions stored in different locations of a memory device,different memory devices, or different computers, which togetherimplement the described functionality of the module. Indeed, a modulemay include a single instruction or many instructions, and may bedistributed over several different code segments, among differentprograms, and across several memory devices. Some embodiments may bepracticed in a distributed computing environment where tasks areperformed by a remote processing device linked through a communicationsnetwork. In a distributed computing environment, software modules may belocated in local and/or remote memory storage devices. In addition, databeing tied or rendered together in a database record may be resident inthe same memory device, or across several memory devices, and may belinked together in fields of a record in a database across a network.

Reference throughout this specification to “an example” means that aparticular feature, structure, or characteristic described in connectionwith the example is included in at least one embodiment. Thus,appearances of the phrase “in an example” in various places throughoutthis specification are not necessarily all referring to the sameembodiment.

As used herein, a plurality of items, structural elements, compositionalelements, and/or materials may be presented in a common list forconvenience. However, these lists should be construed as though eachmember of the list is individually identified as a separate and uniquemember. Thus, no individual member of such list should be construed as ade facto equivalent of any other member of the same list solely based onits presentation in a common group without indications to the contrary.In addition, various embodiments and examples may be referred to hereinalong with alternatives for the various components thereof. It isunderstood that such embodiments, examples, and alternatives are not tobe construed as de facto equivalents of one another, but are to beconsidered as separate and autonomous representations.

Furthermore, the described features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments. In thefollowing description, numerous specific details are provided, such asexamples of materials, frequencies, sizes, lengths, widths, shapes,etc., to provide a thorough understanding of the embodiments. Oneskilled in the relevant art will recognize, however, that theembodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, etc. In otherinstances, well-known structures, materials, or operations are not shownor described in detail to avoid obscuring aspects of embodiments.

It should be recognized that the systems described herein includedescriptions of specific embodiments. These embodiments can be combinedinto single systems, partially combined into other systems, split intomultiple systems or divided or combined in other ways. In addition, itis contemplated that parameters/attributes/aspects/etc. of oneembodiment can be used in another embodiment. Theparameters/attributes/aspects/etc. are merely described in one or moreembodiments for clarity, and it is recognized that theparameters/attributes/aspects/etc. can be combined with or substitutedfor parameters/attributes/etc. of another embodiment unless specificallydisclaimed herein.

Although the foregoing has been described in some detail for purposes ofclarity, it will be apparent that certain changes and modifications maybe made without departing from the principles thereof. It should benoted that there are many alternative ways of implementing both theprocesses and apparatuses described herein. Accordingly, the presentembodiments are to be considered illustrative and not restrictive, andthe description is not to be limited to the details given herein, butmay be modified within the scope and equivalents of the appended claims.

What is claimed is:
 1. An apparatus of an access and mobility managementfunction (AMF) configured to provide mobile terminated (MT) datatransport in a communication network, the apparatus comprising: a memoryinterface to send or receive, to or from a memory device, a protocoldata unit (PDU) session identifier (ID); and a processor to: process anon-access stratum (NAS) message and the PDU session ID from a sessionmanagement function (SMF), the NAS message comprising downlink data froma function in the communication network; generate an integrity protectedand encrypted downlink NAS transport message comprising the PDU sessionID and the NAS message from the SMF; and forward the downlink NAStransport message to an access node for delivery to a user equipment(UE) associated with the PDU session ID; wherein the PDU session is ofan unstructured type, reliable data service (RDS) is enabled, andwherein the downlink NAS transport message includes an indication thatRDS acknowledgement is requested.
 2. The apparatus of claim 1, theprocessor to process an uplink NAS message from the UE, the uplink NASmessage comprising an acknowledgement of the downlink data.
 3. Theapparatus of claim 1, wherein the function in the communication networkcomprises a network exposure function (NEF) or a user plane function(UPF).
 4. The apparatus of claim 1, the processor to, in response todetermining that the UE is in a connection management (CM) idle state,before forwarding the downlink NAS transport message to the access nodefor delivery to the UE, send a paging message to the access node toperform paging of the UE.
 5. The apparatus of claim 1, further includinga radio front-end module and one or more antennas coupled to theradio-front-end module to communicate with the SMF and the access node.6. An apparatus of an access and mobility management function (AMF)configured to provide mobile terminated (MT) data transport in acommunication network, the apparatus comprising: means for processing anon-access stratum (NAS) message and a protocol data unit (PDU) sessionidentifier (ID) from a session management function (SMF), the NASmessage comprising downlink data from a function in the communicationnetwork; means for generating an integrity protected and encrypteddownlink NAS transport message comprising the PDU session ID and the NASmessage from the SMF; and means for forwarding the downlink NAStransport message to an access node for delivery to a user equipment(UE) associated with the PDU session ID, wherein the PDU session is ofan unstructured type, reliable data service (RDS) is enabled, andwherein the downlink NAS transport message includes an indication thatRDS acknowledgement is requested.
 7. The apparatus of claim 6, furtherincluding means for processing an uplink NAS message from the UE, theuplink NAS message comprising an acknowledgement of the downlink data.8. The apparatus of claim 6, wherein the function in the communicationnetwork comprises a network exposure function (NEF) or a user planefunction (UPF).
 9. The apparatus of claim 6, further including meansfor, in response to a determination that the UE is in a connectionmanagement (CM) idle state, before forwarding the downlink NAS transportmessage to the access node for delivery to the UE, sending a pagingmessage to the access node to perform paging of the UE.
 10. A method tobe performed at an apparatus of an access and mobility managementfunction (AMF) configured to provide mobile originated (MO) datatransport in a communication network, the method comprising: processinga non-access stratum (NAS) message from a user equipment (UE), the NASmessage comprising a protocol data unit (PDU) session identifier (ID)and uplink data; checking integrity of and decrypt the NAS messagecomprising the PDU session ID and the uplink data; determining, based onthe PDU session ID, a session management function (SMF); routing the PDUsession ID and the uplink data to the SMF for forwarding to a functionin the communication network; generating a downlink NAS transportmessage to communicate to the UE, the downlink NAS transport messagecomprising the PDU session ID and downlink data provided from thefunction in the communication network through the SMF; and determiningport numbers in a header of the NAS message from the UE to identify anapplication on an originator and an application on a receiver of the NASmessage from the UE.
 11. The method of claim 10, further including, inresponse to an indication that the UE supports reliable data service(RDS), determining whether the header in the NAS message from the UEindicates a PDU of the NAS message requires no acknowledgement, requiresacknowledgment, or includes an acknowledgement of prior downlink data.12. The method of claim 10, wherein the downlink data comprises anacknowledgement of the uplink data.
 13. The method of claim 10, whereinthe function in the communication network comprises a network exposurefunction (NEF) or a user plane function (UPF).
 14. The method of claim10, wherein the NAS message from the UE further comprises releaseassistance information to indicate whether the NAS message comprises alast PDU expected, and wherein the method further includes releasing,based on the release assistance information indicating that the NASmessage comprises a last PDU expected, a connection between the UE andan access node.
 15. An apparatus of an access and mobility managementfunction (AMF) configured to provide mobile originated (MO) datatransport in a communication network, the apparatus comprising: meansfor processing a non-access stratum (NAS) message from a user equipment(UE), the NAS message comprising a protocol data unit (PDU) sessionidentifier (ID) and uplink data; means for checking integrity of anddecrypt the NAS message comprising the PDU session ID and the uplinkdata; means for determining, based on the PDU session ID, a sessionmanagement function (SMF); means for routing the PDU session ID and theuplink data to the SMF for forwarding to a function in the communicationnetwork; means for generating a downlink NAS transport message tocommunicate to the UE, the downlink NAS transport message comprising thePDU session ID and downlink data provided from the function in thecommunication network through the SMF; and means for determining portnumbers in a header of the NAS message from the UE to identify anapplication on an originator and an application on a receiver of the NASmessage from the UE.
 16. The apparatus of claim 15, further includingmeans for, in response to an indication that the UE supports reliabledata service (RDS), determining whether the header in the NAS messagefrom the UE indicates a PDU of the NAS message requires noacknowledgement, requires acknowledgment, or includes an acknowledgementof prior downlink data.
 17. The apparatus of claim 15, wherein thedownlink data comprises an acknowledgement of the uplink data.
 18. Theapparatus of claim 15, wherein the function in the communication networkcomprises a network exposure function (NEF) or a user plane function(UPF).
 19. The apparatus of claim 15, wherein the NAS message from theUE further comprises release assistance information to indicate whetherthe NAS message comprises a last PDU expected, the apparatus furthercomprising means for releasing, based on the release assistanceinformation indicating that the NAS message comprises a last PDUexpected, a connection between the UE and an access node.